On Sat, 3 Dec 2016 00:12:53 -0800
Daniel Campbell <z...@gentoo.org> wrote:

> On 12/02/2016 11:55 PM, Michał Górny wrote:
> > On Fri, 2 Dec 2016 23:21:34 -0800
> > Daniel Campbell <z...@gentoo.org> wrote:
> >   
> >> On 12/02/2016 10:45 AM, Ian Stakenvicius wrote:  
> >>> On 02/12/16 01:31 PM, Ciaran McCreesh wrote:    
> >>>> On Fri, 2 Dec 2016 13:24:29 -0500
> >>>> Mike Gilbert <flop...@gentoo.org> wrote:    
> >>>>> On Fri, Dec 2, 2016 at 1:10 PM, Ciaran McCreesh
> >>>>> <ciaran.mccre...@googlemail.com> wrote:    
> >>>>>> On Fri, 2 Dec 2016 13:02:48 -0500
> >>>>>> Mike Gilbert <flop...@gentoo.org> wrote:      
> >>>>>>> The devmanual states:
> >>>>>>>
> >>>>>>> The name section should contain only lowercase non-accented
> >>>>>>> letters, the digits 0-9, hyphens, underscores and plus characters.
> >>>>>>> Uppercase characters are strongly discouraged, but technically
> >>>>>>> valid.
> >>>>>>>
> >>>>>>> https://devmanual.gentoo.org/ebuild-writing/file-format/index.html
> >>>>>>>
> >>>>>>>
> >>>>>>> Why are uppercase characters strongly discouraged?
> >>>>>>>
> >>>>>>> Wouldn't it make sense to follow upstream's naming convention?      
> >>>>>>
> >>>>>> What's upstream's naming convention for Firefox?    
> >>>>>
> >>>>> I have no idea. What's your point?    
> >>>>
> >>>> That naming conventions are generally complicated and a mess, and that
> >>>> no-one wants to have to remember whether it's firefox, Firefox, or
> >>>> FireFox.
> >>>>    
> >>>
> >>> It's also more convenient at the consone to just type everything
> >>> lowercase.  I expect that's the primary reason it's discouraged.
> >>>
> >>>
> >>>
> >>>     
> >> That seems the most likely to me as well.
> >>
> >> We could make a more "user friendly" feature by setting up bash
> >> completion for package names, but that sounds a) daunting, b)
> >> error-prone, and c) probably not worth the time spent writing the
> >> script(s) necessary.  
> > 
> > There is a bash completion script for that for a long time now.
> > However, it no longer works correctly with new bash-completion versions
> > and it seems that nobody cares enough to fix it.
> >   
> Oh, that's good to know. I didn't find anything relevant with
> 'bash-completion' in its name in the tree. Where should I look for this
> script?

gentoo-bashcomp

-- 
Best regards,
Michał Górny
<http://dev.gentoo.org/~mgorny/>

Attachment: pgpqMJgma0PmT.pgp
Description: OpenPGP digital signature

Reply via email to