1 |
Jason Stubbs wrote: |
2 |
> On Saturday 03 December 2005 13:27, Marius Mauch wrote: |
3 |
> |
4 |
>>Andrea Carpani wrote: |
5 |
>> |
6 |
>>>... |
7 |
>>>and I have binary packages for both c-4.0 and c-4.1 when I emerge |
8 |
>>>virtual-2.0.ebuild i get c-4.1.ebuild but if I emerge virtual-1.0 I get |
9 |
>>>both c-4.0 (required as a dependency for virtual-1.0) and c-4.1 (as a |
10 |
>>>dep for a-2.0 who gets the latest c even though c-4.0 would have |
11 |
>>>satisfied the dependency. |
12 |
>>> |
13 |
>>>Any info on how to avoid this? |
14 |
>> |
15 |
>>It might be helpful if you'd post a real example and not some invalid |
16 |
>>pseudo-ebuild syntax. |
17 |
> |
18 |
> |
19 |
> Not really necessary. He has an ebuild that says "=kde-3.4.0* =xorg-x11-6.7*" |
20 |
> which pulls in kde first which then pulls in "xorg-x11" which portage |
21 |
> resolves to xorg-x11-6.8 after which portage processes xorg-x11-6.7* to |
22 |
> xorg-x11-6.7 and both versions get installed (the latter overwriting the |
23 |
> former and causing the former to be unmerged). It's essentially bug 1343. |
24 |
|
25 |
Hmm, you must have seen more than I did then as I couldn't spot any atom |
26 |
in the mail. Or you're just better at guessing ;) |
27 |
|
28 |
Marius |
29 |
-- |
30 |
gentoo-portage-dev@g.o mailing list |