On Fri, Dec 02, 2016 at 08:09:31PM -0800, Nick Vinson wrote: > > On 12/02/2016 10:28 AM, Ulrich Mueller wrote: > >>>>>> On Fri, 2 Dec 2016, Mike Gilbert 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? > > > > No, because even for the most common packages it would be hard to > > guess what the actual convention is. For example, is it GCC (used on > > its web page and in documentation) or gcc (name of the command and > > displayed by gcc --version)? > > > > If we allow uppercase, then should we also allow two packages in the > > tree whose names differ only in character case? > > If Gentoo chose to perfectly match GNU's naming with GCC, then the > ebuild should be GCC-<version>.ebuild.
I'm thinking about it more from the development standpoint, so that we don't need things like the MY_Pn, MY_P and S manipulation you see in dev-python/configargparse. William
signature.asc
Description: Digital signature
