From owner-svn-ports-head@freebsd.org Fri Oct 14 02:08:19 2016 Return-Path: Delivered-To: svn-ports-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0EE6DC10FEA; Fri, 14 Oct 2016 02:08:19 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 028327CC; Fri, 14 Oct 2016 02:08:19 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1033) id 00DC410DB; Fri, 14 Oct 2016 02:08:19 +0000 (UTC) Date: Fri, 14 Oct 2016 02:08:18 +0000 From: Alexey Dokuchaev To: Mathieu Arnold Cc: Boris Samorodov , Boris Samorodov , ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r423799 - in head/devel: . arduino-sevseg Message-ID: <20161014020818.GA32457@FreeBSD.org> References: <201610112119.u9BLJZUg025971@repo.freebsd.org> <78824109-0639-384b-3ec5-3e9245607d98@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.6.1 (2016-04-27) X-BeenThere: svn-ports-head@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: SVN commit messages for the ports tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Oct 2016 02:08:19 -0000 On Wed, Oct 12, 2016 at 02:53:04PM +0200, Mathieu Arnold wrote: > Le 12/10/2016 ?? 14:44, Boris Samorodov a ??crit : > > 12.10.2016 12:59, Mathieu Arnold пишет: > >> Le 11/10/2016 ?? 23:19, Boris Samorodov a ??crit : > >>> +PORTNAME= arduino-sevseg > >>> > >>> +GH_PROJECT= SevSeg > >> This should be: > >> > >> PORTNAME=SevSeg > >> PKGNAMEPREFIX=Arduino- > > > > I like our tradition to have port names in lower case. There are > > exceptions but this port AFAIK is not among them. > > There is no such tradition. Yes there is, please stop misguiding people Mathieu. This tradition is commongly seen throughout entire Unix heritage and is omnipresent, from login names to APIs. You may prefer c:\Documents and Settings\User Joe but most of us don't. Yes, this also applies to port and package names. > The rule is that PORTNAME follows upstream's naming. The only exception > when the port installs a single utility and that utility is lowercased. There are plenty if counterexamples to what you say, Firefox and PostgreSQL would be a good start to reconsider your views. > Now, this, here, is some library that does not install a binary, so that > rule applies, follow upstream's choice of naming. This is what we do for CPAN packages and others that 1) include a lot of ports, 2) have an established naming convention of their own, 3) many of them are common dependencies and it helps to have similar package names with popular GNU/Linux distros. For some random unattached port it's almost always better tolower() it, (ir)regardless of whether it is a single utility, library, game with a lot of resources, or anything else. ./danfe