From owner-svn-ports-all@freebsd.org Sat Apr 18 08:01:22 2020 Return-Path: Delivered-To: svn-ports-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 17D3D2C0D4B; Sat, 18 Apr 2020 08:01:22 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49454x6mXqz3FkP; Sat, 18 Apr 2020 08:01:21 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1033) id D730411077; Sat, 18 Apr 2020 08:01:21 +0000 (UTC) Date: Sat, 18 Apr 2020 08:01:21 +0000 From: Alexey Dokuchaev To: Kubilay Kocak Cc: Baptiste Daroussin , ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org, python Subject: Re: svn commit: r531949 - in head/devel: . libuInputPlus Message-ID: <20200418080121.GB40012@FreeBSD.org> References: <202004171637.03HGbWMf060426@repo.freebsd.org> <20200418022541.GA6251@FreeBSD.org> <70db47ee-0448-467b-92e6-278ad8bae2ab@localhost> <20200418071022.GA40012@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-BeenThere: svn-ports-all@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: SVN commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Apr 2020 08:01:22 -0000 On Sat, Apr 18, 2020 at 05:49:43PM +1000, Kubilay Kocak wrote: > 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. > > The Python example is in fact actually an example for the opposite. Well, what I was saying there is that Python ports are distinctive, large group of ports that may prefer to follow some specific naming convention. Perhaps I should've just mentioned CPAN. > 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. Awesome, so you guys also follow the default sane convention. That's good. ./danfe