jesse wrote:
> [dropped off even the p5p cc, since I'm going to ask an idiot question]
>
> Why not create inc::Module::Build which probes for inc/Module-Build if
> it's there and prefers taht, otherwise uses the system M::B?
Indeed, you could. It's where these sort of quick hacks develop towards.
Let's call that "stage two". :)
> It'll save lots of pain when someone discoveres that the oneliner is
> busted in some obscure idiotic circumstance. AND it could even
> eventually be used to override the inc/ version if an AWFUL bug is later
> discovered.
Unfortunately it doesn't get around the oneliner problem, everyone will still
have it hard coded in their distributions. And you do need to probe for the
installed Module::Build version in a separate process because we have no way
to unload a module. Or we manually go through @INC and scrape $VERSION out.
The former at least has the benefit of being a known quantity and once it
works, it always works. $VERSION scraping will always be a heuristic.
Anyhow, shoving it into a module at least encapsulates the problem and makes
it easy to upgrade.
--
87. If the thought of something makes me giggle for longer than 15
seconds, I am to assume that I am not allowed to do it.
-- The 213 Things Skippy Is No Longer Allowed To Do In The U.S. Army
http://skippyslist.com/list/
