Hi all. Here's my problem. I'm using a lot binary packages of "in portage" and "custom created" ebuilds. I have a "virtual" ebuild I use that contains only dependencies and I use this one to merge given versions of packages all in one shot: sort of a shanpshot of a given moment in time (sort of tag).
Eg: virtual-1.0.ebuild contains RDEPEND=" a-2.0.ebuild b-3.0.ebuild c-4.0.ebuild d-5.0.ebuild " So that emerge -K virtual-1.0 emerges all a,b,c,d on given versions and: virtual-2.0.ebuild contains RDEPEND=" a-2.1.ebuild b-3.1.ebuild c-4.1.ebuild d-5.1.ebuild " My problem is that if a-2.0.ebuild and a-2.1.ebuild contain RDEPEND=" >c-1.0 " and I have binary packages for both c-4.0 and c-4.1 when I emerge virtual-2.0.ebuild i get c-4.1.ebuild but if I emerge virtual-1.0 I get both c-4.0 (required as a dependency for virtual-1.0) and c-4.1 (as a dep for a-2.0 who gets the latest c even though c-4.0 would have satisfied the dependency. Any info on how to avoid this? -- [EMAIL PROTECTED] http://www.carpani.net Andrea Carpani .a.c. -- Andrea Carpani <[EMAIL PROTECTED]> -- [email protected] mailing list
