Date: Tue, 26 Dec 2017 09:18:02 -0600 From: Jason Bacon <bacon4000@gmail.com> To: Adam Weinberger <adamw@adamw.org>, yuri@freebsd.org Cc: Alexey Dokuchaev <danfe@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: <0e81e642-9157-d8e3-12f2-af08724accf6@gmail.com> In-Reply-To: <E628F4ED-8707-4094-8849-AAF51477583E@adamw.org> References: <201712182143.vBILhFND023143@repo.freebsd.org> <20171224135522.GA1693@FreeBSD.org> <6fa2551a-dee7-9388-07fc-6539800b6c5a@freebsd.org> <20171225112028.GA61880@FreeBSD.org> <dd23ef4c-5136-d6b8-f638-95347ed3a357@freebsd.org> <E628F4ED-8707-4094-8849-AAF51477583E@adamw.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/25/17 15:29, Adam Weinberger wrote: >> On 25 Dec, 2017, at 11:56, Yuri <yuri@freebsd.org >> <mailto:yuri@freebsd.org>> wrote: >> >> On 12/25/17 03:20, Alexey Dokuchaev wrote: >>> "Official" names look good in documentation and port description, but not >>> so as port's directory and PORTNAME. The fact that it was earlier named >> >> >> Yeah .... let's just disagree on that one. >> > > Alexey and Tijl are not wrong, Yuri. Alexey has been crucial in > maintaining standards in the ports tree, and his input deserves far > more than a dismissive response. > > I’ve been very torn when approving these reviews. On the one hand, the > port should be named what end-users call it, and (using the SCIP > example) the project refers to itself as SCIP 100% of the time. But on > the other hand, FreeBSD convention has ALWAYS been names that match > what’s installed, and controverting that breaks precedent and violates > POLA. > > I’ve been approving these because that’s what the projects call > themselves. But that’s not sufficient reason to break tradition, and > it’s a conversation that has to involve far more input than you and me. > > For now, please focus on ports without capitalization questions until > the way forward is clear. > > # Adam > > > -- > Adam Weinberger > adamw@adamw.org <mailto:adamw@adamw.org> > http://www.adamw.org 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. 2. Same for "what's installed". Does this refer to the main command/library? x11/lilyterm provides an example. Upstream distname is LilyTerm, but the binary is lilyterm as are the directory name in the docs it installs). I've seen cases where even the binary and other installed files use different case, though. 3. Should PORTNAME match the port directory name? @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. I was in a similar discussion years ago where the apparent winner favored all lowercase directory names and PORTNAME matching the upstream dist, so I've been following that convention ever since. A clear policy in PHB would be really helpful... - Confused new developer -- Earth is a beta site.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0e81e642-9157-d8e3-12f2-af08724accf6>