| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
|
| 5 |
Is there plan to based the dependencies of portage on the real files required |
| 6 |
instead of other packages required? At the current time I use the fake |
| 7 |
package installed option but was wondering if such enhancement was planned |
| 8 |
inside gentoo portage. |
| 9 |
|
| 10 |
ex: I install my software by hand without using gentoo it created a libtest.so |
| 11 |
and is inside the /usr/lib, then I merge a package which require libtest.so |
| 12 |
now I could set a dependency on a package containing the libtest.so but I'd |
| 13 |
like not to install or re-install that lib. Today I say that the package |
| 14 |
containing the libtest.so is install even if it is not from gentoo point of |
| 15 |
view but it would be nice that Gentoo Portage figure it out by itself. Also |
| 16 |
if the libtest.so wasn't to be found, then Gentoo Portage would have a way to |
| 17 |
figure out which package will generate such libtest.so needed. |
| 18 |
|
| 19 |
I kind of understand that doing this trick require a lot more information |
| 20 |
about dependency both compile and runtime inside the ebuild files and |
| 21 |
therefore I think that adding this feature would also require tools to figure |
| 22 |
out compile/runtime dependencies. Probably the configure and makefile are |
| 23 |
containing most of that information already and could be extracted from |
| 24 |
there. |
| 25 |
|
| 26 |
It's not a P1 feature, more likely a very low priority feature but I believe |
| 27 |
it could add even more flexibility to Portage. |
| 28 |
|
| 29 |
- -- |
| 30 |
|
| 31 |
Yannick Koehler |
| 32 |
-----BEGIN PGP SIGNATURE----- |
| 33 |
Version: GnuPG v1.0.6 (GNU/Linux) |
| 34 |
Comment: For info see http://www.gnupg.org |
| 35 |
|
| 36 |
iD8DBQE9ic6NfuKOJNEyL1URAjpqAJsH45dOhPBmeQHoMv/0qk8FcDplWACgkbn1 |
| 37 |
NxxA6ctVf2SjXQpIK2Fb/qU= |
| 38 |
=wQIB |
| 39 |
-----END PGP SIGNATURE----- |
Archives