No, I'm probably not being clear enough. What I'm suggesting they do is supply a legacy Makefile.PL that works totally independant of having M::B installed at all. Even if it's named something else (e.g. Makefile.Legacy.PL) to keep it out of the way, that would be fine. In my case perhaps M::B would have worked to generate one with the "traditional" option -- I don't know. I didn't want to find out because it failed 'make test', I couldn't fix it, so I didn't trust it. In my current work environment I've found I need to be very conservative, so YMMV. | [reply] |
No, I'm probably not being clear enough. What I'm suggesting they do is supply a legacy Makefile.PL that works totally independant of having M::B installed at all.
No, I'm probably not being clear enough :-)
The the "traditional" create_makefile_pl option in M::B produces a normal Makefile.PL file at distribution time that uses EU::MM. So the package you download from CPAN has a Makefile.PL that you can use without having M::B installed - and a Build.PL if you do have M::B installed.
Hopefully this makes some vague sort of sense :-)
| [reply] |
Ugh. I was unclear, dimwitted and redundant -- I thought this happened at user build time.
<gilda-radner-mode>
Nevermind...
</gilda-radner-mode>
| [reply] [d/l] |