| 1 |
On Fri, Dec 02, 2016 at 04:13:48PM -0500, Mike Gilbert wrote: |
| 2 |
> On Fri, Dec 2, 2016 at 1:47 PM, Michał Górny <mgorny@g.o> wrote: |
| 3 |
> > On Fri, 2 Dec 2016 13:02:48 -0500 |
| 4 |
> > Mike Gilbert <floppym@g.o> wrote: |
| 5 |
> > |
| 6 |
> >> The devmanual states: |
| 7 |
> >> |
| 8 |
> >> The name section should contain only lowercase non-accented letters, |
| 9 |
> >> the digits 0-9, hyphens, underscores and plus characters. Uppercase |
| 10 |
> >> characters are strongly discouraged, but technically valid. |
| 11 |
> >> |
| 12 |
> >> https://devmanual.gentoo.org/ebuild-writing/file-format/index.html |
| 13 |
> >> |
| 14 |
> >> |
| 15 |
> >> Why are uppercase characters strongly discouraged? |
| 16 |
> >> |
| 17 |
> >> Wouldn't it make sense to follow upstream's naming convention? |
| 18 |
> > |
| 19 |
> > I'd say keeping things lowercase makes sense for end user packages. For |
| 20 |
> > pure dependencies with consistent conventions (e.g. perl), it makes |
| 21 |
> > sense to keep upstream's naming. |
| 22 |
> > |
| 23 |
> |
| 24 |
> This seems like a reasonable approach. Thanks. |
| 25 |
|
| 26 |
So, should we clean up / rename packages that do not follow this as we |
| 27 |
find them, like my ConfigArgParse example? |
| 28 |
|
| 29 |
William |
Archives