| 1 |
Hello, |
| 2 |
|
| 3 |
I know of two cases of circular deps that can be solved -- as far as I |
| 4 |
know -- only by bundling: |
| 5 |
|
| 6 |
1. dev-util/pkgconfig <-> dev-libs/glib:2, |
| 7 |
|
| 8 |
2. dev-util/cmake <-> dev-libs/jsoncpp. |
| 9 |
|
| 10 |
The former is solved via having USE=internal-glib on pkgconfig, |
| 11 |
the latter is yet unsolved [1]. |
| 12 |
|
| 13 |
I suspect we can expect more of this kind of issues in non-systemd |
| 14 |
world over time, and I feel like it'd be good to develop a generic |
| 15 |
policy for handling them. Something that could avoid having users go |
| 16 |
through this on a case-by-case basis. |
| 17 |
|
| 18 |
I think the simplest solution would be to develop a generic USE flag |
| 19 |
that would only serve the purpose of forcing bundled dependencies for |
| 20 |
bootstrapping/initial install. |
| 21 |
|
| 22 |
We have already: |
| 23 |
|
| 24 |
build - !!internal use only!! DO NOT SET THIS FLAG YOURSELF!, used for |
| 25 |
creating build images and the first half of bootstrapping [make stage1] |
| 26 |
|
| 27 |
bootstrap - !!internal use only!! DO NOT SET THIS FLAG YOURSELF!, used |
| 28 |
during original system bootstrapping [make stage2] |
| 29 |
|
| 30 |
However, since both are marked for 'internal use only', I don't think |
| 31 |
it's a good idea to use them here. So I guess we need a new flag. Does |
| 32 |
anyone have suggestions how to name it? |
| 33 |
|
| 34 |
Any other ideas? |
| 35 |
|
| 36 |
[1]:https://bugs.gentoo.org/show_bug.cgi?id=546130 |
| 37 |
|
| 38 |
-- |
| 39 |
Best regards, |
| 40 |
Michał Górny |
Archives