On Oct 8, 2006, at 10:26 PM, Eric Wilhelm wrote:
An automatic error during "./Build dist" is the strong remedy.
Aside from the fact that I am apparently unable to correctly configure
my mail client, what is wrong with this approach?
http://www.nntp.perl.org/group/perl.module.build/380
From a functional standpoint, I imagine that automagically adding
dependencies to META.yml would work. However, I don't like the idea
of MB surreptitiously sneaking in a dependency without my knowing
about it. IMO, all dependencies should be explicitly spelled out by
the author under requires and build_requires.
In a perfect world, the functions in M::B that need CBuilder would be
quarantined off, and you'd have to ask for CBuilder to access them.
Then this auto-detection stuff wouldn't be necessary. It's only
needed because M::B used to have its own C stuff before it got
yanked, and the kludge to fix the situation ought to do minimum harm.
To follow the automagic-add approach out ad absurdum, should it
automatically detect that you need other things besides CBuilder?
That's sounds like a lot of cruft getting crammed into M::B, a distro
which is already exceedingly featureful. And no matter how elaborate
the guessing apparatus, it'll guess wrong some of the time... so
there will have to be an override mechanism. Instread of all that,
why not just leave the programmer in charge?
Marvin Humphrey
Rectangular Research
http://www.rectangular.com/
