svn commit: r531949 - in head/devel: . libuInputPlus

Alexey Dokuchaev danfe at freebsd.org
Sat Apr 18 07:10:22 UTC 2020


On Sat, Apr 18, 2020 at 06:28:06AM +0000, Baptiste Daroussin wrote:
> I never understood why portname should be lowercase if upstream considers
> it should not, there are precedent of mixed case (actually respecting
> upstream will).

For the same reasons we don't have `www/Firefox', `databases/PostgreSQL',
etc.  It does not look unixish.  There are few special cases when it is
indeed desirable to use mixed cased names, e.g. CPAN packages, Python
modules, those things with established naming convention of their own, when
we bring lots of them to our ports and want to stay more or less consistent
with popular GNU/Linux distributions, but those are isolated groups.

For some random unattached port it's almost always better tolower() it.
We're Unix, and lowercase is preferred by default.  This tradition is
commonly seen throughout entire Unix heritage and is omnipresent, be it
login names, hier(7), or most APIs.  This naturally applies to port and
package names.  Please don't break this consistency.

./danfe


More information about the svn-ports-all mailing list