svn commit: r436025 - in head/lang: . OpenCoarrays OpenCoarrays/files

[Alexey Dokuchaev]

On Tue, Mar 14, 2017 at 01:42:42PM +0100, Mathieu Arnold wrote:
> Le 14/03/2017 ?? 13:25, Alexey Dokuchaev a ??crit :
> > On Tue, Mar 14, 2017 at 01:11:30PM +0100, Tijl Coosemans wrote:
> >> On Tue, 14 Mar 2017 12:54:57 +0100 Mathieu Arnold <mat at FreeBSD.org>
> >> wrote:
> >>> This was uncalled for.
> >>>
> >>> The *only* reason we use to lowercase the name of a port when upstream
> >>> is not lowercased is if it provides a lowercased binary to run.
> > No, we always prefer lowercase, with a few known exceptions.  Every sane
> > packaging ecosystem does the same (GNU/Linux distributions, Homebrew, you
> > name it).
> 
> Well, no. *You* prefer lowercase, but *we*, as a project, do not. But
> you have been badgering people long enough that everyone thinks it is a
> rule.

We're Unix, so yes we do.  It is part of our cultural identity and can be
seen in command and user names, APIs, header files, just about everywhere.
It naturally applies to package and ports' names, and vast majority of
existing and new ports arrive lowercased -- and not because I'm "badgering"
ports' creators and maintainers, but because they also want it that way.

I'm simply trying to keep it all consistent, hense I ask people to rename
mixed-case ports.

./danfe