Chris Dolan wrote:
On Jun 5, 2007, at 8:00 PM, Andy Lester wrote:
Yes. Second-order dependencies are beyond your control. You will
have false dependencies when an underlying module changes.
Say that Mech has dependency on HTML::Wango, which in turn has a
dependency on Test::Tango. So my dependencies are listed as
HTML::Wango => 1.00,
Test::Tango => 1.00,
SCENARIO 1: The maintainer of Foo::Wango decides that Test::Tango is
unnecessary, and does without it. He released HTML::Wango 1.02.
Someone installing Mech must now install HTML::Wango and Test::Tango,
although NOTHING in the chain requires Test::Tango.
[snip]
Still, scenario 1 is the killer.
SCENARIO 3: Combine 1 & 2.
The CPAN.pm default is "ask" and we
know that most of the time most people just take defaults.
Yes, I agree that Andy's first point is persuasive. (I also agree with
Chris that most people just accept the defaults.)
So I will include only the first-order dependencies in Makefile.PL. But
I will list the second-order dependencies in the README and in the POD.
Gentlemen, thanks for your rapid response!
jimk
