Re: The danger of blowing away newer modules.

On Wed, Aug 29, 2001 at 05:00:12AM -0400, Michael G Schwern wrote:
> Let's say I'm putting together an SDK for silly modules (which I am)
> and I throw Symbol::Approx::Sub in.  It has a dependency on
> Devel::Symdump.  Well, Devel::Symdump is totally unrelated to the rest
> of the SDK, but we must resolve the dependency so it has to go in.
> 
> Now the question is, what if they already have Devel::Symdump
> installed and *it's a newer version*?  I'm been trying to think of an
> easy way that the SDK will only install a certain piece of itself if
> there's not already an equal or never version installed.  And do it
> with a minimum of work to the SDK maintainer.
> 
> Ideas?

Sounds like something MakeMaker should take care of.

Tim.