| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Spider (D.m.D. Lj.) wrote: |
| 5 |
| Why? Because they just install the hard RDEPEND, so if you have a system |
| 6 |
| installed from binaries, you get working linking, but nothing will |
| 7 |
| compile for the system. |
| 8 |
|
| 9 |
Right, until you actually install the build-time deps. Not unexpected or |
| 10 |
surprising after thinking about it. |
| 11 |
|
| 12 |
| Theese level of inheritance bugs are a ripe minefield for the whole |
| 13 |
| distribution, and one that will severely damage the distribution as a |
| 14 |
| whole. one way of solving it is to go through each and every |
| 15 |
| top-level application and violently scan all its included files, and all |
| 16 |
| files included from those headers in turn, in order to get the |
| 17 |
| dependencies right. |
| 18 |
| |
| 19 |
| The other is to fix the level closest to the breakage by making sure |
| 20 |
| that headers are treated like libraries. |
| 21 |
| |
| 22 |
| |
| 23 |
| Hope I'm making this clear enough, its fairly early. |
| 24 |
|
| 25 |
So there's a harder but more technically correct solution (specifying |
| 26 |
includes as DEPENDs where necessary), and an easier but not as correct |
| 27 |
solution (considering build-time dependencies as run-time dependencies). |
| 28 |
|
| 29 |
At least that's how things look from my perspective. |
| 30 |
|
| 31 |
Thanks, |
| 32 |
Donnie |
| 33 |
-----BEGIN PGP SIGNATURE----- |
| 34 |
Version: GnuPG v1.4.2 (GNU/Linux) |
| 35 |
|
| 36 |
iD8DBQFDXcf6XVaO67S1rtsRAvQ7AKCCFU45+c6Davjb6WW8P1Xh2ymmowCggDxt |
| 37 |
1xSuZbKtdsRy+kk/22rQysE= |
| 38 |
=QrS4 |
| 39 |
-----END PGP SIGNATURE----- |
| 40 |
-- |
| 41 |
gentoo-dev@g.o mailing list |
Archives