Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 18 Apr 2020 17:49:43 +1000
From:      Kubilay Kocak <koobs@FreeBSD.org>
To:        Alexey Dokuchaev <danfe@freebsd.org>, Baptiste Daroussin <bapt@freebsd.org>
Cc:        ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org, python <python@FreeBSD.org>
Subject:   Re: svn commit: r531949 - in head/devel: . libuInputPlus
Message-ID:  <a8d5b0aa-8397-5abf-eefa-6befafb1ce3a@FreeBSD.org>
In-Reply-To: <20200418071022.GA40012@FreeBSD.org>
References:  <202004171637.03HGbWMf060426@repo.freebsd.org> <20200418022541.GA6251@FreeBSD.org> <70db47ee-0448-467b-92e6-278ad8bae2ab@localhost> <20200418071022.GA40012@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 18/04/2020 5:10 pm, Alexey Dokuchaev wrote:
> 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
> 

The Python example is in fact actually an example for the opposite.

Python package (the scheme for their declaration) names are case 
insensitive, with regard to their name declarations both upstream at the 
package registry, as well as in dependency declarations in packages 
themselves.

The reason we lower-case as a policy in Python is to reduce human, 
contributor, maintainer, committer error by reducing/removing the 
impedance mismatch between the case insensitivity upstream vs case 
sensitivity in ports.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a8d5b0aa-8397-5abf-eefa-6befafb1ce3a>