Eric Hall <opendarwin....@...> writes:
> Ah, another case where that can fail is if module Y requires
> module X at a particular version. If a calling script already imported
> module X (at a lower-than-required version), I don't think module Y
> will re-import the "right" version.
This seems to be correct.
use YYY;
use lib '${prefix}/lib/perl5/vendor_perl/';
use YYY VERSION;
@INC = @lib::ORIG_INC;
results in an error if VERSION is the newer version.
In runs fine, however, if the first "use YYY" is commented out.
I was hoping to avoid modifying @INC.
It seemed that ${prefix}/bin/perl should not behave differently depending
on which p5 ports are installed.
I am out of ideas on how to make that happen however.
How about this:
* Modify @INC so the newer p5 ports are found first.
* Do not add conflicting p5 port as dependencies unless the newer version is
actually required (mitigate the potential problems).
* Prepend p5- to the conflicting man pages.
_______________________________________________
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
