There are several packages that do not follow the usual naming of perl module packages. For example the following packages are using all lower case: net-server net-sftp net-ssh-perl text-autoformat text-reform text-template text-wrapper Whereas almost the entire portage collection of perl modules uses perl-style caps: Net-Daemon Net-DNS Net-Jabber Net-RawIP Net-XWhois Text-Aspell Test-Class Text-CharWidth Text-ChaSen Text-WikiFormat Just makes it a pain to keep remembering/looking up which ones need to be written in which way, for eg. overlays, portage.keywords files. Since in many places case sensitivity counts, it would be nice to stick to one format throughout the package tree for perl modules.
Well, the original policy is that all package names should be lower case...
And that would be even better if they just followed the overall standard of lower case, as opposed to creating an odd one out case for Perl packages.
dev-perl has been grandfathered in this case, and no one has reversed that decision in the last 2 years. Of the packages that use lower case, a few are because $P is actually lower case (such as dev-perl/version), most were because before dev-perl was grandfathered we were asked to add new packages in all lower case.
1) Policy wasn't considering a category with a couple hundred packages with upstream uppercase naming. 2) The perl herd isn't big enough to handle a task of that proportion. 3) Not only that, but then we'd have to change all the packages that depend on perl modules. Considering that perl is not a mildly utilized package (spamasassin uses it..), that would be an insane ammount of work, which, see #2. 4) Personally speaking, I'd rather be fixing package bumps, severe bugs, etc. The cost simply don't simply outweigh the benefits here.
