Date: Sat, 18 Apr 2020 07:10:22 +0000 From: Alexey Dokuchaev <danfe@freebsd.org> To: Baptiste Daroussin <bapt@freebsd.org> Cc: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r531949 - in head/devel: . libuInputPlus Message-ID: <20200418071022.GA40012@FreeBSD.org> In-Reply-To: <70db47ee-0448-467b-92e6-278ad8bae2ab@localhost> References: <202004171637.03HGbWMf060426@repo.freebsd.org> <20200418022541.GA6251@FreeBSD.org> <70db47ee-0448-467b-92e6-278ad8bae2ab@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20200418071022.GA40012>