Hi all,
We've run into a Build.PL vs Makefile.PL problem with cpanminus. The
situation is that if M::B requires anything with a Build.PL file, that
it becomes impossible to bootstrap.
The easy thing would be to remove the Build.PL from ExtUtils::ParseXS,
ExtUtils::CBuilder, etc (but only because we have comaint on those.)
Slightly more difficult would be to remove them from our 'requires'
(since they are not strictly required) and insert them in
build_requires as needed (in META.yml and MYMETA.yml). I think this
would actually be more correct. David, what was the logic for these
recent additions to 'requires'?
We went back and forth about a few possible workarounds in #toolchain,
but those all get thrown out because a client should not assume that
Build.PL uses Module::Build.
So, if -e "Build.PL", a cpan client should only ever need to do:
1. satisfy configure_requires
2. run Build.PL
If we break that, we've created a bug in M::B.
Thanks,
Eric
--
As an old bass player friend of mine used to say: throw money, don't
clap.
--Tony Parisi
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
