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