1 |
On Tuesday 27 December 2005 12:08, Brian Harring wrote: |
2 |
> On Tue, Dec 27, 2005 at 03:54:38AM +0100, Carsten Lohrke wrote: |
3 |
> > On Tuesday 27 December 2005 03:40, Brian Harring wrote: |
4 |
> > > The version of digikam being merged requires slot=3.5- it should be |
5 |
> > > depending on libk* slot=3.5, also, no? |
6 |
> > |
7 |
> > No! It (and also its dependencies) can be built against each 3.x slot. |
8 |
> > |
9 |
> > > As long as the information is represented dependency wise, portage |
10 |
> > > should be able to handle it fine. Just need to have that info there. |
11 |
> > |
12 |
> > It can't be handled dependency wise, because what is interesting is |
13 |
> > against which KDE version the relevant ebuilds are actually installed. |
14 |
> |
15 |
> So note the comment in the email you are responding to about locking |
16 |
> down the used dep/rdeps for an install. |
17 |
> |
18 |
> Via that, could lock down the slot it was compiled against. Bit more |
19 |
> to it then that, but the concerns your raising *again* are not |
20 |
> use/slot based, your pointing at other portage faults (thus please |
21 |
> seperate those concerns from use/slot). |
22 |
|
23 |
I may be missing something, but I can't see how this will resolve Carsten's |
24 |
issue. From what I can tell, the ebuilds would be laid out something like: |
25 |
|
26 |
digikam:DEPEND="|| ( kdelibs:3.5 kdelibs:3.4 ) libkipi libkexif" |
27 |
libkipi:DEPEND="|| ( kdelibs:3.5 kdelibs:3.4 )" |
28 |
libkexif:DEPEND="|| ( kdelibs:3.5 kdelibs:3.4 )" |
29 |
|
30 |
If all three of those packages were first built against kdelibs:3.4 and then |
31 |
kdelibs:3.5 became available then rebuilding any one of them without |
32 |
rebuilding the others will break digikam. I can't see how it's directly |
33 |
represented in the metadata unless you want to overload the meaning of SLOT. |
34 |
|
35 |
If overloading, dependencies would be flattened (meaning "|| ( kdelibs:3.5 |
36 |
kdelibs:3.4 )" would have became "kdelibs:3.4" for the original install) |
37 |
within the installed package database but there's also there's the |
38 |
implication that only one slot of a package be allowed in a connected set of |
39 |
nodes. Is that what you're getting at? |
40 |
|
41 |
-- |
42 |
Jason Stubbs |
43 |
-- |
44 |
gentoo-dev@g.o mailing list |