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