On Tue, Dec 27, 2005 at 03:54:38AM +0100, Carsten Lohrke wrote: > On Tuesday 27 December 2005 03:40, Brian Harring wrote: > > The version of digikam being merged requires slot=3.5- it should be > > depending on libk* slot=3.5, also, no? > > No! It (and also its dependencies) can be built against each 3.x slot. > > > As long as the information is represented dependency wise, portage > > should be able to handle it fine. Just need to have that info there. > > It can't be handled dependency wise, because what is interesting is against > which KDE version the relevant ebuilds are actually installed.
So note the comment in the email you are responding to about locking down the used dep/rdeps for an install. Via that, could lock down the slot it was compiled against. Bit more to it then that, but the concerns your raising *again* are not use/slot based, your pointing at other portage faults (thus please seperate those concerns from use/slot). ~harring
pgpCRl3G2aOe0.pgp
Description: PGP signature
