svn commit: r456674 - in head/graphics: . libQGLViewer libQGLViewer/files
Jason Bacon
bacon4000 at gmail.com
Tue Dec 26 15:18:05 UTC 2017
On 12/25/17 15:29, Adam Weinberger wrote:
>> On 25 Dec, 2017, at 11:56, Yuri <yuri at freebsd.org
>> <mailto:yuri at 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 at adamw.org <mailto:adamw at 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.
More information about the svn-ports-head
mailing list