The danger of blowing away newer modules.

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?


-- 

Michael G. Schwern   <[email protected]>    http://www.pobox.com/~schwern/
Perl6 Quality Assurance     <[email protected]>	     Kwalitee Is Job One
It sure is fun masturbating.
	http://www.unamerican.com/