in reply to Why does CPAN default to "ask" when grabbing dependencies? Why not just follow?

Because it's safer.

If you've ever tried dealing with a 'new' sysadmin, who decides to install a new package, which has a dependancy on a module with a different version, and that breaks something else on the box, and you have to spend the weekend trying to track down what they changed, because they won't fess up.

(It was ~5 years ago ... the module that got modified was Net::LDAP ... I don't remember what triggered the whole thing, but somehow, the script that we used for automating account creation for a 35k user mail system just stopped working ... luckily, it was a pure perl module, so I grabbed the older version from the development box.)

Where is it safe to follow? Any time you're not replacing anything that's already in existance ... but that may not be a file rewrite ... if you have multiple module locations, something might find the newer module first. Luckily, in those cases, it's easier to recover.

  • Comment on Re: Why does CPAN default to "ask" when grabbing dependencies? Why not just follow?

Replies are listed 'Best First'.
Re^2: Why does CPAN default to "ask" when grabbing dependencies? Why not just follow?
by tphyahoo (Vicar) on Dec 25, 2005 at 18:50 UTC
    Very enlightening, thanks. Apprently a fix for this "new version breaks modules dependent on old version" problem is something larry is taking very seriously in perl6. Or at least something he talked about in an interview: