| 1 |
Am Wed, 18 Feb 2004 00:39:12 -0500 |
| 2 |
schrieb "Paul Smith" <pausmith@××××××××××××××.com>: |
| 3 |
|
| 4 |
|
| 5 |
> Anyone have any good ideas about how to manage this? |
| 6 |
> |
| 7 |
|
| 8 |
Hmm -- maybe split one of those ebuilds up into |
| 9 |
|
| 10 |
foo-fake.ebuild |
| 11 |
(with only headers and wrapper libs that provide empty functions |
| 12 |
so not depending on anything but allowing the other to build (but not run) against) |
| 13 |
|
| 14 |
and foo.ebuild |
| 15 |
(with the full package inside) |
| 16 |
|
| 17 |
then let both provide "virtual/foo-bar-dependencies" and let bar.ebuild depend on it, |
| 18 |
theb let foo.ebuild depend on "bar" |
| 19 |
|
| 20 |
so when emerging foo -- it should first install foo-fake, then bar, and the foo |
| 21 |
but i dont know if portage can handle this. |
| 22 |
|
| 23 |
would there be a way to tell portage that foo-fake is to be replaced by foo when installing it-- |
| 24 |
this way having some sort of "priority" for provide virtual/stuff ? |
| 25 |
|
| 26 |
Corvus |
| 27 |
|
| 28 |
-- |
| 29 |
gentoo-dev@g.o mailing list |
Archives