On Fri, Dec 02, 2016 at 04:13:48PM -0500, Mike Gilbert wrote: > On Fri, Dec 2, 2016 at 1:47 PM, Michał Górny <mgo...@gentoo.org> 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? > > > > I'd say keeping things lowercase makes sense for end user packages. For > > pure dependencies with consistent conventions (e.g. perl), it makes > > sense to keep upstream's naming. > > > > This seems like a reasonable approach. Thanks.
So, should we clean up / rename packages that do not follow this as we find them, like my ConfigArgParse example? William
signature.asc
Description: Digital signature
