Date: Thu, 14 Dec 2017 14:00:24 +0000 From: Alexey Dokuchaev <danfe@FreeBSD.org> To: Dan Langille <dan@langille.org> Cc: Dan Langille <dvl@FreeBSD.org>, ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r456223 - in head/www: . Stikked Stikked/files Message-ID: <20171214140024.GA86804@FreeBSD.org> In-Reply-To: <499A3288-D06B-4AC8-9E91-7963146028E9@langille.org> References: <201712131744.vBDHicEP086668@repo.freebsd.org> <20171213175339.GB96646@FreeBSD.org> <499A3288-D06B-4AC8-9E91-7963146028E9@langille.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Dec 13, 2017 at 07:49:59PM -0500, Dan Langille wrote: > > On Dec 13, 2017, at 12:53 PM, Alexey Dokuchaev <danfe@FreeBSD.org> wrote: > > On Wed, Dec 13, 2017 at 05:44:38PM +0000, Dan Langille wrote: > >> New Revision: 456223 > >> URL: https://svnweb.freebsd.org/changeset/ports/456223 > >> > >> Log: > >> Add Stikked, a PHP-based Pastebin > >> > >> Added: > >> head/www/Stikked/ > >> head/www/Stikked/Makefile (contents, props changed) > > > > If it's PHP module, shouldn't it have some php- prefix? > > It is not a module, but it does PHP. Ah, OK then. > As for the prefix, can you point me to that in the documentation please? No prefix needed for general purpose ports (i.e. not "batteries"). > Just using PHP doesn't mean you prepend php to the name. Right. > > Otherwise it's badly named (should be www/Stikked -> www/stikked, > > PORTNAME=stikked). > > It is appropriately named based on the upstream project. There is no > prohibition or convention on capitals. It is not appropriately named; there is a convention tolower() ports' names, this tradition is commonly seen throughout entire Unix heritage and is omnipresent, from login names to header files and APIs. This also naturally applies to port and package names. We do follow upstream 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, thus it helps to have similar package names with popular GNU/Linux distributions. For some random unattached port it's almost always better tolower() it. Mixed-case port and package names, with an aforementioned exception, do no good but bring inconsistency to the collection and confuse users. ./danfe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20171214140024.GA86804>