cvs commit: ports/devel/hs-BNFC Makefile distinfo pkg-descr pkg-plist ports/devel/hs-filemanip Makefile distinfo pkg-descr pkg-plist ports/textproc/hs-lhs2tex Makefile distinfo pkg-descr pkg-plist

[Pav Lucistnik]

On 2011/05/04 00:46, b. f. wrote:
> On 5/3/11, Pav Lucistnik<pav at freebsd.org>  wrote:
>> Doug Barton píše v po 02. 05. 2011 v 12:40 -0700:
>>> On 05/02/2011 00:57, Gabor PALI wrote:
>>>>    On 05/02/11 09:44, Doug Barton wrote:
>>>>> On 05/01/2011 22:31, Ashish SHUKLA wrote:
>>>>>>      devel/bnfc ->    devel/hs-BNFC
>>>>>
>>>>> I thought we didn't do new upper-case port names on purpose?
>>>>>
>>>>
>>>> It stems from HackageDB [1].  The port will be converted to a
>>>> bsd.cabal.mk [2] consumer soon.
>>>>
>>>>
>>>> [1] http://hackage.haskell.org/package/BNFC
>>>> [2] http://www.freebsd.org/cgi/cvsweb.cgi/ports/lang/ghc/bsd.cabal.mk
>>>
>>> I'm sorry, I don't understand this response. I realize that there are
>>> some software packages that have upper-case letters in their names.
>>> However, my understanding is that we are not using upper-case letters
>>> for new portnames. Is my understanding incorrect?
>>
>> My understanding is that the first letter must be lowercase, next
>> letters are allowed to be uppercase if there's a good reason ie.
>> upstream naming.
>>
>
> We have some existing conventions that don't conform to this rule, and
> will affect the addition of new ports.  The CRAN ports use R-cran-*,
> and more of these ports will be added.  Do you want us to move these
> to r-cran-* ?

It's a guideline not a law.

No I don't think these need to be changed retroactively.  Actually R is 
such a well recognized software name while r means nothing, so I'd not 
want to see math/R renamed either.

-- 
Pav Lucistnik <pav at oook.cz>
               <pav at FreeBSD.org>