Jason Stubbs wrote:
On Saturday 03 December 2005 13:27, Marius Mauch wrote:
Andrea Carpani wrote:
...
and I have binary packages for both c-4.0 and c-4.1 when I emerge
virtual-2.0.ebuild i get c-4.1.ebuild but if I emerge virtual-1.0 I get
both c-4.0 (required as a dependency for virtual-1.0) and c-4.1 (as a
dep for a-2.0 who gets the latest c even though c-4.0 would have
satisfied the dependency.
Any info on how to avoid this?
It might be helpful if you'd post a real example and not some invalid
pseudo-ebuild syntax.
Not really necessary. He has an ebuild that says "=kde-3.4.0* =xorg-x11-6.7*"
which pulls in kde first which then pulls in "xorg-x11" which portage
resolves to xorg-x11-6.8 after which portage processes xorg-x11-6.7* to
xorg-x11-6.7 and both versions get installed (the latter overwriting the
former and causing the former to be unmerged). It's essentially bug 1343.
Hmm, you must have seen more than I did then as I couldn't spot any atom
in the mail. Or you're just better at guessing ;)
Marius
--
[email protected] mailing list
