From owner-svn-ports-head@freebsd.org Thu Dec 14 14:00:25 2017 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 D8FF1E80F47; Thu, 14 Dec 2017 14:00:25 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B7B74651ED; Thu, 14 Dec 2017 14:00:25 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1033) id 029CD1BBD9; Thu, 14 Dec 2017 14:00:24 +0000 (UTC) Date: Thu, 14 Dec 2017 14:00:24 +0000 From: Alexey Dokuchaev To: Dan Langille Cc: Dan Langille , 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> References: <201712131744.vBDHicEP086668@repo.freebsd.org> <20171213175339.GB96646@FreeBSD.org> <499A3288-D06B-4AC8-9E91-7963146028E9@langille.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <499A3288-D06B-4AC8-9E91-7963146028E9@langille.org> User-Agent: Mutt/1.9.1 (2017-09-22) X-BeenThere: svn-ports-head@freebsd.org X-Mailman-Version: 2.1.25 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: Thu, 14 Dec 2017 14:00:25 -0000 On Wed, Dec 13, 2017 at 07:49:59PM -0500, Dan Langille wrote: > > On Dec 13, 2017, at 12:53 PM, Alexey Dokuchaev 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