I'm fine with you removing the copies associated with me too. That was
quite a genealogy of the software releases Neil!
//Ed
PS. Hi Bill & Galen 👋
On 9/19/20 6:44 PM, Bill Birthisel wrote:
Hi Neil,
I'm fine with removing the ancient copy associated with me.
-bill (BBIRTH)
On 9/19/20 5:16 PM, Neil Bowers wrote:
Hi Galen,
I’m one of the PAUSE admins. I working through situations where there
are permissions oddities with CPAN distributions, or conflicts
between two or more distributions.
This affects your MARC/XML releases. It looks like this is what
happened in the past:
* User BBIRTH first released the distribution MARC-XML, which
contained the module MARC::XML
* User ESUMMERS took over the distribution, and renamed the
MARC::XML module to be MARC::File::XML, and added MARC::File::SAX
to the distribution. But the distribution name renamed MARC-XML.
* User KADOS took over, and did a number of releases, the last one
in 2007. Same distribution name, same two modules.
* You took over the distribution in 2009, and in the first three
releases, didn’t change any of the naming.
* You did a 1.0 release of MARC-XML, where you dropped
MARC::File::SA, as you were using XML::LibXML.
* Then in 2017 you renamed the distribution to be MARC-File-XML, to
match the module name, as per PAUSE’s expectations.
Because the old MARC-XML releases are still in your directory (and
those of the previous authors), if a user searches on MetaCPAN, they
can appears find two different modules called MARC::File::XML, but
really one is an earlier version of the other.
I think the best way to resolve this situation is:
* For you to delete the old releases of MARC-XML from your author
directory on PAUSE
* For BBIRTH to delete MARC-XML 0.4 from his author directory on PAUSE
* For ESUMMERS to delete all releases of MARC-XML from his author
directory on PAUSE
* For KADOS to similarly delete all releases of MARC-XML from his
author directory on PAUSE
Then we’ll end up with just the latest version of MARC::File::XML
showing up on MetaCPAN, and much less chance of someone accidentally
installing an old release.
I’ve copied BBIRTH, ESUMMERS, and KADOS in on this email as well.
If you’re all happy with this plan, I can schedule the deletion of
the old releases on your behalf. Is that ok?
Cheers,
Neil
