Re: obscure <constraints> question

On 18/2/2002 20:51, Will Partain wrote:

> Why is this an error?  Imagine you had a package for 'foo-wrapper'
> which let you choose between 5 versions

Hah. Good point. You got me there.

In that case I'd say that the more specific constraint still satisfies the
more general one, but where there's multiple more specific constraints, you
go with the higher version number.

So a dependency on 'foo' is satisfied by 'foo--1.2.3' (presumably, that
would appear in the queriable information for that dependency). However, in
the case that some other field requires 'foo--1.2.3' and 'foo--1.2.4', then
the field is satisfied by 'foo--1.2.4'.

I would presume this fits with the scheme if we specify 'foo' only - does it
pick the highest version to satisfy the constraint?

Interesting question is, if we have the following two dependencies:

    foo = 1.2.3
    foo > 1.2.4

and we have a 'foo--1.2.5', then does this require both 'foo--1.2.3' and
'foo--1.2.5'? I would say yes.

Question is: how hard is it to solve these constraints?

:-j

-- 
jonathan hogg, one good idea ltd, 131 queen margaret dr., glasgow g20 8pd
http://www.onegoodidea.com/ tel:+44-(0)7976-614338 fax:+44-(0)7970-537451