On Tue, 21 May 2002 23:38:06 +0300, Ville =?ISO-8859-1?Q?Skytt=E4?= said:
Versioned requirements could be useful, especially for packages. We
do
know that package A needs version x.xx of package B to work properly, so
PUI could handle these for the user, like "If you're installing this,
you will also need to upgrade that." A simple
"greater-than-or-equal-to" dependency would probably be enough, at least
to begin with.
Remember to allow for "blocking" releases as well, so you can express things
like:
"If you're installing Frobozz 1.13 or later, you also need Moby-Grape 1.3.4
or later, but *NOT* Moby-Grape 2.0".
/Valdis (who has gotten burnt when Foo 2.0 got installed because it was "later"
than Foo 1.4, but the changed API was Just Not The Same ;)