svn commit: r436025 - in head/lang: . OpenCoarrays OpenCoarrays/files
Garance A Drosehn
drosih at rpi.edu
Thu Mar 16 23:19:16 UTC 2017
On 14 Mar 2017, at 8:25, Alexey Dokuchaev wrote:
> On Tue, Mar 14, 2017, Tijl Coosemans wrote:
>> On Tue, 14 Mar 2017 Mathieu Arnold <mat at FreeBSD.org> wrote:
>>> This was uncalled for.
>>>
>>> The *only* reason we use to lowercase the name of a port when
>>> upstream is not lowercased is if it provides a lowercased
>>> binary to run.
>
> No, we always prefer lowercase, with a few known exceptions.
> Every sane packaging ecosystem does the same (GNU/Linux
> distributions, Homebrew, you name it).
First let me start by saying that I personally prefer having all the
ports names being lowercase. But to ignore my personal preference
for moment, note that:
# port list OpenCoarrays
OpenCoarrays @1.8.2 science/OpenCoarrays
same if you search for the lowercase name:
# port list opencoarrays
OpenCoarrays @1.8.2 science/OpenCoarrays
for this specific port, macports does not use the lowercase name.
As near as I can tell, 'homebrew' does not have this port at all.
I'm not much of a linux wizard, but https://www.rpmfind.net/
suggests that there isn't an RPM for it either.
So the one packaging system which has this port, has it listed
under the mixed-case name. And as long as the search in FreeBSD
is case-insensitive, then I have no strong opinion about which
name should be used in our ports collection.
On 14 Mar 2017, at 8:42, Mathieu Arnold wrote:
>
> The *only* reference to case in the porter's handbook is in an
> example, and only for single binary ports.
>
If this is going to be source of contention over personal opinions,
then maybe the porter's handbook needs to include some more explicit
statement.
--
Garance Alistair Drosehn = drosih at rpi.edu
Senior Systems Programmer or gad at FreeBSD.org
Rensselaer Polytechnic Institute; Troy, NY; USA
More information about the svn-ports-head
mailing list