svn commit: r423799 - in head/devel: . arduino-sevseg
Boris Samorodov
bsam at passap.ru
Wed Oct 12 13:46:18 UTC 2016
12.10.2016 16:32, Boris Samorodov пишет:
> 12.10.2016 15:53, Mathieu Arnold пишет:
>> Le 12/10/2016 à 14:44, Boris Samorodov a écrit :
>>> 12.10.2016 12:59, Mathieu Arnold пишет:
>>>> Le 11/10/2016 à 23:19, Boris Samorodov a écrit :
>>>>> +PORTNAME= arduino-sevseg
>>>>>
>>>>> +GH_PROJECT= SevSeg
>>>> This should be:
>>>>
>>>> PORTNAME=SevSeg
>>>> PKGNAMEPREFIX=Arduino-
>>> I like our tradition to have port names in lower case. There are
>>> exceptions but this post AFAIK is not among them.
>>
>> There is no such tradition.
>
> Yes, there is. The Porters Handbook (Table 5.1. at the end of the page):
> https://www.freebsd.org/doc/en/books/porters-handbook/makefile-naming.html
Hm, I see what you mean. This table has a note "No uppercase names for
single programs". Unfortunately, not very helpful note.
It may be a good idea to document the port naming guides.
> Those examples are old one (more then 10 years).
>
>> The rule is that PORTNAME follows upstream's naming. The only exception
>> when the port installs a single utiliity and that utility is lowercased.
>>
>> For example, if sysutils/lsof's distfile was called, say, LsOF, PORTNAME
>> would still be lsof because the utility is in lower case.
>>
>> Now, this, here, is some library that does not install a binary, so that
>> rule applies, follow upstream's choice of naming.
>
> Is it your POV? Mine just disagrees.
--
WBR, bsam
More information about the svn-ports-head
mailing list