Ciaran McCreesh wrote:

> On Sat, 28 Jun 2008 19:57:11 +0200
> Tiziano Müller <dev-zero@g.o> wrote:
>> I miss two things here:
>> a) What happens in case of DEPEND="", RDEPEND=">=cat/bar-2:=" ? Is
>> that defined? If yes, what does it mean? If not, what shall be the
>> package managers behaviour?
> 
> := only makes sense when something is both a DEPEND and an RDEPEND.
> Actual behaviour, for Paludis, is that it rewrites := deps to :=blah
> when writing to VDB any time it can, and leaves anything it can't as :=
> deps. Verifying sanity of := use is left to developers and the QA tool.
... and the spec.

> 
>> b) It is not said that a package depending on "|| ( cat/bar:2
>> cat/bar:3 )" then really uses cat/bar:3 if available, it might as
>> well use cat/bar:2 for one reason or another. It might be clearer if
>> we have slots named "stable", "unstable". In such a case a package
>> depending on cat/bar might decided to use cat/bar:stable if available
>> instead of cat/bar:unstable. So, the spec should either state that
>> the package must use the best matching version or we need another way
>> for such cases, like a function to explicitly tell the pm which slot
>> has been used.
> 
> The only sensible thing you can do with multiple matches on := slots
> (and ||=, if that route is taken) is to take the slot of the best
> matching installed version, and require that ebuilds do that too. In
> real world cases, this works just fine.
> 
so, ebuilds should use best_version instead of has_version for example.
That's what I meant and what I miss in the kdebuild-1 spec :-)


-- 
gentoo-dev@g.o mailing list