Date: Tue, 26 Dec 2017 14:47:05 -0600 From: Jason Bacon <bacon4000@gmail.com> To: Alexey Dokuchaev <danfe@FreeBSD.org> Cc: Adam Weinberger <adamw@adamw.org>, 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: <4105e72a-cdd1-c792-7f69-e00bb22d01cb@gmail.com> In-Reply-To: <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> <dd23ef4c-5136-d6b8-f638-95347ed3a357@freebsd.org> <E628F4ED-8707-4094-8849-AAF51477583E@adamw.org> <0e81e642-9157-d8e3-12f2-af08724accf6@gmail.com> <20171226155201.GA90333@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/26/17 09:52, Alexey Dokuchaev wrote: > 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 Clarifying my point #3: When I said "match" I meant in terms of upper/lower case. Are you suggesting that PORTNAME should also be reduced to lowercase to match the directory name? -- Earth is a beta site.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4105e72a-cdd1-c792-7f69-e00bb22d01cb>