1 |
On Sat, 3 Dec 2016 00:12:53 -0800 |
2 |
Daniel Campbell <zlg@g.o> wrote: |
3 |
|
4 |
> On 12/02/2016 11:55 PM, Michał Górny wrote: |
5 |
> > On Fri, 2 Dec 2016 23:21:34 -0800 |
6 |
> > Daniel Campbell <zlg@g.o> wrote: |
7 |
> > |
8 |
> >> On 12/02/2016 10:45 AM, Ian Stakenvicius wrote: |
9 |
> >>> On 02/12/16 01:31 PM, Ciaran McCreesh wrote: |
10 |
> >>>> On Fri, 2 Dec 2016 13:24:29 -0500 |
11 |
> >>>> Mike Gilbert <floppym@g.o> wrote: |
12 |
> >>>>> On Fri, Dec 2, 2016 at 1:10 PM, Ciaran McCreesh |
13 |
> >>>>> <ciaran.mccreesh@××××××××××.com> wrote: |
14 |
> >>>>>> On Fri, 2 Dec 2016 13:02:48 -0500 |
15 |
> >>>>>> Mike Gilbert <floppym@g.o> wrote: |
16 |
> >>>>>>> The devmanual states: |
17 |
> >>>>>>> |
18 |
> >>>>>>> The name section should contain only lowercase non-accented |
19 |
> >>>>>>> letters, the digits 0-9, hyphens, underscores and plus characters. |
20 |
> >>>>>>> Uppercase characters are strongly discouraged, but technically |
21 |
> >>>>>>> valid. |
22 |
> >>>>>>> |
23 |
> >>>>>>> https://devmanual.gentoo.org/ebuild-writing/file-format/index.html |
24 |
> >>>>>>> |
25 |
> >>>>>>> |
26 |
> >>>>>>> Why are uppercase characters strongly discouraged? |
27 |
> >>>>>>> |
28 |
> >>>>>>> Wouldn't it make sense to follow upstream's naming convention? |
29 |
> >>>>>> |
30 |
> >>>>>> What's upstream's naming convention for Firefox? |
31 |
> >>>>> |
32 |
> >>>>> I have no idea. What's your point? |
33 |
> >>>> |
34 |
> >>>> That naming conventions are generally complicated and a mess, and that |
35 |
> >>>> no-one wants to have to remember whether it's firefox, Firefox, or |
36 |
> >>>> FireFox. |
37 |
> >>>> |
38 |
> >>> |
39 |
> >>> It's also more convenient at the consone to just type everything |
40 |
> >>> lowercase. I expect that's the primary reason it's discouraged. |
41 |
> >>> |
42 |
> >>> |
43 |
> >>> |
44 |
> >>> |
45 |
> >> That seems the most likely to me as well. |
46 |
> >> |
47 |
> >> We could make a more "user friendly" feature by setting up bash |
48 |
> >> completion for package names, but that sounds a) daunting, b) |
49 |
> >> error-prone, and c) probably not worth the time spent writing the |
50 |
> >> script(s) necessary. |
51 |
> > |
52 |
> > There is a bash completion script for that for a long time now. |
53 |
> > However, it no longer works correctly with new bash-completion versions |
54 |
> > and it seems that nobody cares enough to fix it. |
55 |
> > |
56 |
> Oh, that's good to know. I didn't find anything relevant with |
57 |
> 'bash-completion' in its name in the tree. Where should I look for this |
58 |
> script? |
59 |
|
60 |
gentoo-bashcomp |
61 |
|
62 |
-- |
63 |
Best regards, |
64 |
Michał Górny |
65 |
<http://dev.gentoo.org/~mgorny/> |