-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Specify $ENV{PATH} consistency with @INC #1
Comments
2012/3/24 Olivier Mengué
That's a good point. I'll bring it up in Paris at the QA hackathon. David |
Yeah, I had realized this before, but had never seen actual problems because of it. The same goes for manpaths, though that's unlikely to cause any issues. |
@dagolden I will be at the hackathon. |
Awesome. Could you please put this issue on the wiki projects page? David |
Already done, in the "Build.PL" and "Misc CPAN client stuff" section. You are invited to edit the wiki page (you have to login with your Act credentials). |
This is a general CPAN client spec issue, not specific to Build.PL.
In the environment variable section something must be said about $ENV{PATH}: it must be consistent with
@INC
.I'm writing this because some packages fail to install because the CPAN client has modified
$ENV{PERL5LIB}
to add some temporarylib
paths, but did not modify PATH to add thebin
orscript
dirs. This cause problems for distributions that rely on Perl scripts instead of modules, as we can get trouble if there is a mismatch between the script and its supporting modules (example: running an older script with the newer modules, or finding the module but not the newer script).Here is an example issue: https://rt.cpan.org/Ticket/Display.html?id=75376
The text was updated successfully, but these errors were encountered: