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