Guy Hulbert wrote: > Because perl modules can install their own dependencies
Out of the several TENS OF THOUSANDS of module installs that I've gone through, I've noticed very few which don't either: rely on CPAN.pm (or CPANPLUS) to install dependencies; or ask the user whether to install them and CPAN.pm's default is to *not* automatically install dependencies, but to ask the user whether to install them. So the only way dependencies can be installed automatically is if you've chosen for that to happen. Those few exceptions are for when you try to install Foo::Bar which depends on libfoobar or on some alien executable, so Makefile.PL fetches that for you too. The one example I can think of off the top of my head is Text::BibTeX, which also downloads and builds btparse for you. I happen to think that it doing that is a Good Thing. It's user-friendly. And it shouldn't have any effect on any change control system worthy of the name. > his concern is > other people affecting *his* choices. He only gets to dictate how I write my code if he's paying me. -- David Cantrell | Official London Perl Mongers Bad Influence PERL: Politely Expressed Racoon Love
