On Thu, Nov 19, 2009 at 12:19 PM, Steffen Mueller > However, looking
at the CPAN Testers Matrix for the last two dev releases, I
> see a lot of FAIL and UNKNOWN in the test reports. See for yourself:
>
> http://matrix.cpantesters.org/?dist=PAR-Packer 0.992_05
> http://matrix.cpantesters.org/?dist=PAR-Packer 0.992_04
>
> It's still fine in 0.992_03 and earlier:
> http://matrix.cpantesters.org/?dist=PAR-Packer 0.992_03
>
> Now, I'm starved for time as usual. Are there any volunteers willing to
> check the FAIL and UNKOWN test reports against the changes between 0.992_03
> and 0.992_04 to see what made PAR::Packer so fragile?

Hi Steffen,

I had a brief look at the linux column., esp. the
UNKNOWN: make failed with "Can't locate PAR/Heavy.pm in @INC" entries.

Is it possible that the latest CPAN.pm has changed the way
the configure_requires parameter works,
i.e. when are missing requires/config_requires are resolved?

It looks as if CPAN 1.9402 works this way:

(1) satisfy all config_requires
(2) perl Makefile.PL
(3) satisfy requires
(4) make
...

Now "perl Makefile.PL" builds (from @INC) a list of -Idir
options that are burned into Makefile. Later, these are
passed to myldr/static which uses these directories to find
modules like PAR::Heavy. Now PAR is _not_ listed in"configure_requires",
hence its temporay build directory is not in @INC at (2).
PAR _is_ listed in "requires", hence it is downloaded and built
during (3) and its temporay build directory is in @INC at (4).
But that's too late.

To fix: either add PAR (and possibly others) to "config_requires"
or generate the parameters for myldr/static dynamically at make time.

Cheers, Roderich

Reply via email to