Hello Neil, I tested, packaged, and pushed current versions of XAO::* modules to CPAN. That fixed the base.pm vs Base.pm issue, but it still reports indexing issues because of files in testcases/ overlapping between packages.
I know you said I could move them to t/ to avoid indexing, but at the moment I would really like to avoid that. I need to move testing code from obsolete Test::Unit to something better and that might take a while. Using "testcases" is embedded in a couple of places with the current setup, hard to change. I am just afraid that if I need to work on that I might not find time for a while :( Is there a way to hint CPAN to not index files in testcases/ ? Thanks! Andrew. On Wed, Apr 19, 2017 at 7:13 AM, Neil Bowers <neil.bow...@cogendo.com> wrote: > Hi Andrew, > > Thanks for the detailed note. I've been neglecting CPAN, sorry. The > version on GitHub is much more current and is updated for case insensitive > file systems. I will try to push a CPAN update in the next couple of days. > > > This is just a gentle reminder on this :-) > > Cheers, > Neil > > On Mar 8, 2017 2:59 PM, "Neil Bowers" <neil.bow...@cogendo.com> wrote: > >> Hi Andrew, >> >> I’m one of the PAUSE admins. I’m working through tidying up permissions >> conflicts that have been caused by the fact that PAUSE now consider package >> names case insensitively (due to case-insensitive filesystems, as on >> Windows and MacOS X). >> >> You have permissions on testcases::Base, which is released as part of >> XAO-Base, and also have permissions on testcases::base, which is released >> as part of XAO-Web. >> >> From looking at your distributions, it looks like these modules shouldn’t >> be installed? >> >> In XAO-Base, the module is in directory testcases/. The convention now is >> for all tests to live in t/, and PAUSE will automatically not index any >> modules it finds in there. So refactoring your directory structure to >> follow that convention would let us drop the permissions on testcases:: >> >> Are you happy & able to release an updated version of one or both of >> these distributions, to resolve the conflict? >> > >
