| 1 |
Ok... this discussion is missing my initial point that is how to |
| 2 |
provide binary dependency and avoid many crashes we have now with |
| 3 |
almost no effort. |
| 4 |
|
| 5 |
My initial proposal was to, after compile and before install is done, |
| 6 |
we should parse linker information and check for each library it |
| 7 |
depends, which package-version provides it and then mark the just |
| 8 |
compiled package runtime-dependent on them. If the dependency was not |
| 9 |
installed by portage, then issue a warning/error and take some action |
| 10 |
(ask user, abort or ignore) |
| 11 |
|
| 12 |
Pros: |
| 13 |
- it would avoid many crashes we have now because we remove packages |
| 14 |
that others depend on. |
| 15 |
- it would avoid many crashes we have now because we update packages |
| 16 |
that others depend on, but are not listed correctly in ebuilds. |
| 17 |
- it would avoid dependency errors caused by missing |
| 18 |
--disable-feature with autoconf-like packages |
| 19 |
|
| 20 |
Cons: |
| 21 |
- it's not the final solution to the problem, as said, interfaces |
| 22 |
would be better... but interfaces would demand much more effort and |
| 23 |
not being automatically generated, would be async and probably |
| 24 |
incorrect at some point |
| 25 |
|
| 26 |
|
| 27 |
-- |
| 28 |
Gustavo Sverzut Barbieri |
| 29 |
-------------------------------------- |
| 30 |
Jabber: barbieri@×××××.com |
| 31 |
MSN: barbieri@×××××.com |
| 32 |
ICQ#: 17249123 |
| 33 |
Skype: gsbarbieri |
| 34 |
Mobile: +55 (81) 9927 0010 |
| 35 |
Phone: +1 (347) 624 6296; 08122692@××××××××××××××.com |
| 36 |
GPG: 0xB640E1A2 @ wwwkeys.pgp.net |
| 37 |
|
| 38 |
-- |
| 39 |
gentoo-portage-dev@g.o mailing list |
Archives