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