Hi, Neil! This module was written as a PoC and never was used in any of production code. As I can see from deps, there is no CPAN modules, that uses it also. After all, for now there is another module LV, that was inspired by lvalue and do more, than my.
So, I renamed lvalue into Sub::Lvalue for the historical reasons and deleted lvalue. -- Mons Anderson <m...@cpan.org> > On 14 сент. 2016 г., at 1:21, Neil Bowers <neil.bow...@cogendo.com> wrote: > > Hi Eric & Mons, > > I’m one of the PAUSE admins. I’m working on resolving conflicts caused by > PAUSE now considering package names case insensitively. This has left us with > some situations where two or more people are owners of namespaces previously > considered distinct, and now considered the same. > > Eric (ASG) has ownership of the namespace “Lvalue”, with the Lvalue module > being on CPAN in the Lvalue distribution. And Mons has ownership of “lvalue”, > which is on CPAN in the lvalue distribution. > > These two packages are now considered the same by PAUSE when looking at > permissions, which means there’s a conflict with your dual ownership, which > means that any releases you do now won’t be indexed. > > There are at least two ways we can resolve this: > > 1. One of you could rename your module and distribution. > Eg Mons, you could switch to Sub::lvalue, or Attribute::lvalue > > 2. You could delete one of your distributions from CPAN. I can do this for > you. > Eg Eric, I notice that your distribution doesn’t install on any Perl > since 5.17.1 > http://matrix.cpantesters.org/?dist=Lvalue > > How would you like to progress? > > PAUSE doesn’t let situations like this occur any more; I’m working on > resolving the existing cases. > > Cheers, > Neil >
