From owner-svn-ports-all@freebsd.org Tue Dec 26 15:52:02 2017 Return-Path: Delivered-To: svn-ports-all@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 46A07E9DC2D; Tue, 26 Dec 2017 15:52:02 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (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 1F3627AA04; Tue, 26 Dec 2017 15:52:02 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1033) id 529512E9E; Tue, 26 Dec 2017 15:52:01 +0000 (UTC) Date: Tue, 26 Dec 2017 15:52:01 +0000 From: Alexey Dokuchaev To: Jason Bacon Cc: Adam Weinberger , yuri@freebsd.org, ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r456674 - in head/graphics: . libQGLViewer libQGLViewer/files Message-ID: <20171226155201.GA90333@FreeBSD.org> References: <201712182143.vBILhFND023143@repo.freebsd.org> <20171224135522.GA1693@FreeBSD.org> <6fa2551a-dee7-9388-07fc-6539800b6c5a@freebsd.org> <20171225112028.GA61880@FreeBSD.org> <0e81e642-9157-d8e3-12f2-af08724accf6@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0e81e642-9157-d8e3-12f2-af08724accf6@gmail.com> User-Agent: Mutt/1.9.2 (2017-12-15) X-BeenThere: svn-ports-all@freebsd.org X-Mailman-Version: 2.1.25 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: Tue, 26 Dec 2017 15:52:02 -0000 On Tue, Dec 26, 2017 at 09:18:02AM -0600, Jason Bacon wrote: > There are some nuances that have to be clarified: > > 1. What exactly does it mean when we talk about "what the developers > call it"? Are we referring to the upstream distname? The title on their > website or in their documentation? Occasionally these things differ. Official name is the one used in documentation, on the website, or in Wikipedia article if there is one. Examples include Firefox, LilyTerm, PostgreSQL, etc. It is the name that should be used, for example, in the port description text (pkg-descr). > 2. Same for "what's installed". Does this refer to the main > command/library? [...] This is largely and usually irrelevant. > 3. Should PORTNAME match the port directory name? Yes, it should, with a few exceptions when e.g. PKGNAMEPREFIX comes to play (examples include CPAN ports, Linux binary ports, etc.). > @mat pointed out that "pkg" is case-insensitive, so case doesn't cause > any inconvenience when dealing with binary packages, but I find it a > nuisance to have to remember case on port directory names. Exactly. It's a nuisance, and that's one of the reasons to keep it as lowercase; again, CPAN ports are valid exception, because that includes a lot of ports that have an established naming convention of their own; many of them are common (omni-Unix) and thus it helps to have similar package names with popular GNU/Linux distributions. > A clear policy in PHB would be really helpful... Yes, it would; but until the PHB is fixed, please stick to currently used most common practices (that is, prefer lowercase unless there are sufficiently strong reasons to do otherwise). Porting a Perl module? Follow CPAN (and existing ports). For some random, unattached (not a part of any cabal) port it is almost always better tolower() its name. (Again, like vast majority existing ports.) ./danfe