| 1 |
Ciaran McCreesh wrote: |
| 2 |
|
| 3 |
> On Sat, 28 Jun 2008 19:57:11 +0200 |
| 4 |
> Tiziano Müller <dev-zero@g.o> wrote: |
| 5 |
>> I miss two things here: |
| 6 |
>> a) What happens in case of DEPEND="", RDEPEND=">=cat/bar-2:=" ? Is |
| 7 |
>> that defined? If yes, what does it mean? If not, what shall be the |
| 8 |
>> package managers behaviour? |
| 9 |
> |
| 10 |
> := only makes sense when something is both a DEPEND and an RDEPEND. |
| 11 |
> Actual behaviour, for Paludis, is that it rewrites := deps to :=blah |
| 12 |
> when writing to VDB any time it can, and leaves anything it can't as := |
| 13 |
> deps. Verifying sanity of := use is left to developers and the QA tool. |
| 14 |
... and the spec. |
| 15 |
|
| 16 |
> |
| 17 |
>> b) It is not said that a package depending on "|| ( cat/bar:2 |
| 18 |
>> cat/bar:3 )" then really uses cat/bar:3 if available, it might as |
| 19 |
>> well use cat/bar:2 for one reason or another. It might be clearer if |
| 20 |
>> we have slots named "stable", "unstable". In such a case a package |
| 21 |
>> depending on cat/bar might decided to use cat/bar:stable if available |
| 22 |
>> instead of cat/bar:unstable. So, the spec should either state that |
| 23 |
>> the package must use the best matching version or we need another way |
| 24 |
>> for such cases, like a function to explicitly tell the pm which slot |
| 25 |
>> has been used. |
| 26 |
> |
| 27 |
> The only sensible thing you can do with multiple matches on := slots |
| 28 |
> (and ||=, if that route is taken) is to take the slot of the best |
| 29 |
> matching installed version, and require that ebuilds do that too. In |
| 30 |
> real world cases, this works just fine. |
| 31 |
> |
| 32 |
so, ebuilds should use best_version instead of has_version for example. |
| 33 |
That's what I meant and what I miss in the kdebuild-1 spec :-) |
| 34 |
|
| 35 |
|
| 36 |
-- |
| 37 |
gentoo-dev@l.g.o mailing list |
Archives