Closed schwern closed 10 years ago
What about giving the "clear winner" the coveted repository name, and giving the others some -A
or -1
or -bis
version?
In every case the offending distribution was done by one author. I went with appending the author's cpanid to the distribution name like readonly-SUMMER, though I only adopted this for the second half.
One of the major concerns in renaming a repository is whether anyone will be able to find it.
Gitpan::Dist->import_releases
now checks to see if a Github repository already exists with the same casing.
Github is case-insensitive. CPAN distribution names are case-sensitive. This is a problem.
If distribution names only differ by case they are probably the same distribution. Usually the solution is to add an entry to the Gitpan config to merge these distributions. Example. ACME-Umlautify vs Acme-Umlautify.
Occasionally they will be different distributions. In this case, only one can be on Github. In this case, the distribution is skipped in the Gitpan config. So far, there has always been a clear winner. Example. Beancounter vs BeanCounter vs beancounter.
This requires human intervention to decide which one to do.