Skip Menu |

This queue is for tickets about the local-lib CPAN distribution.

Report information
The Basics
Id: 72101
Status: resolved
Priority: 0/
Queue: local-lib

People
Owner: Nobody in particular
Requestors: rjbs [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: 2.000003



Subject: docs for build_environment_vars_for is wrong
15:18 <rjbs> DOCS: 15:18 <rjbs> build_environment_vars_for 15:18 <rjbs> Arguments: $path, $interpolate 15:18 <rjbs> CODE: 15:18 <rjbs> sub build_environment_vars_for { my ($class, $path, $deactivating, $interpolate) = @_; other methods may be similarly affected; I did not check -- rjbs
DOCS: build_environment_vars_for Arguments: $path, $interpolate Return value: \%environment_vars ACTUAL RETURN VALUE: a list of pairs, not a hashref -- rjbs
On Tue Nov 01 15:23:15 2011, RJBS wrote: Show quoted text
> 15:18 <rjbs> DOCS: > 15:18 <rjbs> build_environment_vars_for > 15:18 <rjbs> Arguments: $path, $interpolate > 15:18 <rjbs> CODE: > 15:18 <rjbs> sub build_environment_vars_for { my ($class, $path, > $deactivating, > $interpolate) = @_; > > other methods may be similarly affected; I did not check
It looks like this effects CPAN.pm's bootstrapping code. The signature for build_environment_vars_for was actually changed, and CPAN.pm is unintentionally setting the deactivating option because it was written before the change. I have a fix for this, but it's part of a larger patch series. I'm hoping to get it merged soon.
Fixed by removing both the $deactivating and $interpolate options. This should fix CPAN.pm's bootstrapping code. Checking with grep.cpan.me, I didn't see any other modules that would be affected by this. Included in dev release 2.000_000.
Resolved in 2.000003