cvs commit: ports/audio Makefile ports/audio/amarokFS Makefile distinfo pkg-descr pkg-plist ports/audio/amarokFS/files patch-amarokFS-xml.pro

[Alexey Dokuchaev]

On Wed, Jul 04, 2007 at 10:38:06PM +0200, Pav Lucistnik wrote:
> Alexey Dokuchaev p??e v st 04. 07. 2007 v 20:34 +0000:
> > On Wed, Jul 04, 2007 at 10:28:45PM +0200, Pav Lucistnik wrote:
> > > Alexey Dokuchaev p??e v st 04. 07. 2007 v 19:56 +0000:
> > > > On Wed, Jul 04, 2007 at 12:51:46PM -0700, David Thiel wrote:
> > > > > On Wed, Jul 04, 2007 at 07:48:05PM +0000, Alexey Dokuchaev wrote:
> > > > > > We generally try to avoid using upper-case characters in port names.  Do
> > > > > > you mind readding it as, say, `amarok-fs' or `amarok_fs'?
> > > > > 
> > > > > I can change to amarok-fs if it's needed. Should this check be 
> > > > 
> > > > Yes, please change.  Right now it's pretty simple since we have no
> > > > history to preserve, ergo no repocopy required.  Mere cvs rm/add would
> > > > suffice.
> > > 
> > > The policy is that the first letter must be lowercase - amarokFS is
> > 
> > Hehe, you talk Java here.  :-)
> 
> http://www.freebsd.org/doc/en/books/porters-handbook/makefile-naming.html
> 
> Quote:
> 2. The first letter of the name part should be lowercase. (The rest of
> the name may contain capital letters, so use your own discretion when
> you are converting a software name that has some capital letters in it.)

IMHO it should be updated.  There were numerous discussions that raised
this issue before.

> 
> > > fine. Just look at all those perl modules...
> > 
> > Perl (as well as Python et al.) mods are different matter, in terms there's
> > common scheme and overall consistency (which we even share with many
> > GNU/Linux distros).  In most other cases, all-lowercase name looks alot
> > better than ugly `amarokFS'.
> 
> That's your personal opinion.

As a matter of fact, not only mine.

./danfe