1 |
Andrea Carpani wrote: |
2 |
> Hi all. Here's my problem. |
3 |
> |
4 |
> I'm using a lot binary packages of "in portage" and "custom created" |
5 |
> ebuilds. I have a "virtual" ebuild I use that contains only dependencies |
6 |
> and I use this one to merge given versions of packages all in one shot: |
7 |
> sort of a shanpshot of a given moment in time (sort of tag). |
8 |
> |
9 |
> Eg: |
10 |
> |
11 |
> virtual-1.0.ebuild contains |
12 |
> |
13 |
> RDEPEND=" |
14 |
> a-2.0.ebuild |
15 |
> b-3.0.ebuild |
16 |
> c-4.0.ebuild |
17 |
> d-5.0.ebuild |
18 |
> " |
19 |
> |
20 |
> So that emerge -K virtual-1.0 emerges all a,b,c,d on given versions and: |
21 |
> |
22 |
> virtual-2.0.ebuild contains |
23 |
> |
24 |
> RDEPEND=" |
25 |
> a-2.1.ebuild |
26 |
> b-3.1.ebuild |
27 |
> c-4.1.ebuild |
28 |
> d-5.1.ebuild |
29 |
> " |
30 |
> |
31 |
> My problem is that if a-2.0.ebuild and a-2.1.ebuild contain |
32 |
> |
33 |
> RDEPEND=" |
34 |
> |
35 |
>>c-1.0 |
36 |
> |
37 |
> " |
38 |
> |
39 |
> and I have binary packages for both c-4.0 and c-4.1 when I emerge |
40 |
> virtual-2.0.ebuild i get c-4.1.ebuild but if I emerge virtual-1.0 I get |
41 |
> both c-4.0 (required as a dependency for virtual-1.0) and c-4.1 (as a |
42 |
> dep for a-2.0 who gets the latest c even though c-4.0 would have |
43 |
> satisfied the dependency. |
44 |
> |
45 |
> Any info on how to avoid this? |
46 |
|
47 |
It might be helpful if you'd post a real example and not some invalid |
48 |
pseudo-ebuild syntax. |
49 |
|
50 |
Marius |
51 |
-- |
52 |
gentoo-portage-dev@g.o mailing list |