Re: No . in @INC breaks CPAN

On Mon, Nov 14, 2016 at 3:11 PM, Todd Rinaldo wrote: > Howdy, > > I've done a write up of a recent change to blead perl. In the future it > will no longer be possible to count on . being in @INC. This will break > many of the existing CPAN installs. > > It was suggested I send

Re: No . in @INC breaks CPAN

On 11/14/2016 07:39 PM, Aristotle Pagaltzis wrote: * Todd Rinaldo [2016-11-14 15:12]: Long Term We need to fix the CPAN modules themselves. I’m afraid that’s a pipe dream. You can fix the most popular part of CPAN but not even close to everything. There are still

Re: No . in @INC breaks CPAN

* James E Keenan [2016-11-15 14:12]: > Before we polarize ourselves into the camps of "we have to fix all of > CPAN" and "it's hopeless to try to fix CPAN", it's important to > realize that we now have the conceptual tools with which to assess the > scope of the problem.

Re: No . in @INC breaks CPAN

You should probably scan CPAN for other uses of use inc::... My darker memory is throwing up some other potentially false positive red flags. File::ShareDir may be worth a look as it did some fairly funky stuff at build/test time... at one point in its history. Anything file in CPAN with an

Re: No . in @INC breaks CPAN

That doesn't help those of us with a habit of naming our test modules t::Foo::Bar I think there's a fair few things with copies of test modules bundled that way. Adam > On 14 Nov. 2016, at 11:45 am, Karen Etheridge wrote: > > > In this case, adding '.' to the distribution's