Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
If author changes case of already indexed module, change case of all permissions #250
If you release a module
But if you release
I propose that we change PAUSE's behaviour so there can only ever beone case-variant of a namespace listed in
The rest of this illustrates the behaviour I think PAUSE should have.
Let's say ANDK releases module
ANDK then notices that all the other fruits on CPAN are capitalised, so he releases a new version of his dist, with
RSAVAGE points out to ANDK that all the modules in Vegetable:: are lowercase, and people are starting to follow that convention, so with ANDK's blessing, RSAVAGE does a release which switches the name back to
This has been discussed with the PAUSE admins, and @andk agreed we should go ahead with this, unless anyone can think of a reason why this is a bad idea?
Additional data point: LNATION uploaded both ACME-AsciiEmoji-0.01.tar.gz and Acme-AsciiEmoji-0.02.tar.gz and then kept the case in the next versions. But none of these followup-uploads got indexed. The mails he got either did not arrive or were not understood. The status message he got was really poor. Just "Not indexed because of case mismatch."
If a distribution contains both Foo::Bar and FOO::BAR, we will:
… in that order.
(The hardcoded list is no longer expected to be needed, after examining known cases.)