find /usr/portage -name "*[A-Z]*" | grep .ebuild | wc -l 2383 packages use uppercase in the file name and/or category. This situation does not reflect "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." The reader would be interested in a short explanation for this rule at this point too. Should the sentence be "Uppercase characters are technically valid, but should be used sparingly, because ..." Even newer packages use upper case characters in file names for example "dev-perl/Tk" Reproducible: Always
There are some traditional exceptions (perl, php, X), but generally the policy is that uppercase letters are strongly discouraged. Following all the crazy and inconsistent upstream capitalisation rules would add no value. Or, as the old ebuild howto had put it more pointedly: "We have some packages in Portage that don't follow these rules, but *your* packages should." https://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo/xml/htdocs/proj/en/devrel/handbook/hb-guide-ebuild.xml?revision=1.57&view=markup#l244
(In reply to Ulrich Müller from comment #1) > "We have some packages in Portage that don't follow these rules, but *your* > packages should." > > https://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo/xml/htdocs/proj/en/devrel/handbook/hb-guide-ebuild.xml?revision=1.57&view=markup#l244 That link won't work any more. Here's an updated one: https://gitweb.gentoo.org/archive/proj/gentoo.git/tree/xml/htdocs/proj/en/devrel/handbook/hb-guide-ebuild.xml?id=ee09d45ba4e2c8694d7159a08013163d04f3ff75#n244
