cvs commit: ports/x11-fonts Makefile ports/x11-fonts/anonymousPro Makefile distinfo pkg-descr pkg-plist ports/x11-fonts/anonymousPro/files pkg-message.in

[Alexey Dokuchaev]

On Wed, Nov 30, 2011 at 04:16:03PM +0800, wen heping wrote:
> 2011/11/30 Alexey Dokuchaev <danfe at freebsd.org>:
> > On Wed, Nov 30, 2011 at 09:03:13AM +0100, Pawe? P?kala wrote:
> >> "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.)"
> >
> > This section is a bit misleading.  I believe it tries to embrace cases
> > like p5-* ports which are OK to be mixed cased for the reasons of
> > retaining similarity to their CPAN names.  For 99% of other ports this
> > rule should not be applied.
> 
> How about py-* ports ?

Yes, those as well (to a less degree).  I wrote "_like_ p5-* ports" for a
reason.  I used to explain it in detail on a number of occasions in the
past.  To put it shortly, for a large pool of things like extensions,
plugins, etc. -- so called "batteries", especially when meaningful and
consistent upstream naming conventions exist, it is better to follow them as
it helps developers to more easily find appropriate ports in our collection.
It also makes the those names consistent with popular GNU/Linux distros
(modulo perl5 vs. p5 prefixes in case of Perl and Red Hat).  These are good
examples of when unixish "all-lowercase" rule can be bent for a good.

It is also backed up by common sense if one puts enough thinking into it,
I guess. :-)

./danfe