| 1 |
On 26-11-2009 10:37:10 +0000, Duncan wrote: |
| 2 |
> Fabian Groffen posted on Thu, 26 Nov 2009 11:10:09 +0100 as excerpted: |
| 3 |
> |
| 4 |
> > Gentoo Prefix tries to be as much self-sufficient as possible, and hence |
| 5 |
> > applications *must* not reference the host system, unless absolutely |
| 6 |
> > necessary, such as for e.g. /lib/libc.so. |
| 7 |
> |
| 8 |
> Thanks. Host libc /does/ make sense as "absolutely necessary. |
| 9 |
> |
| 10 |
> Are there any less obvious ones, say of the type that might reach out and |
| 11 |
|
| 12 |
Some that you may find are: |
| 13 |
/lib/libm.so |
| 14 |
/lib/libsocket.so |
| 15 |
/lib/libpthread.so |
| 16 |
/lib/libnsl.so |
| 17 |
|
| 18 |
On a side note, we have a question about this in our |
| 19 |
prefix-ebuild-quiz[1] (question 5 from the second section). |
| 20 |
|
| 21 |
> grab an unsuspecting dev trying to make his ebuilds prefix compliant? It |
| 22 |
> seems to me that enumerating all (or all non-corner) cases where |
| 23 |
> referencing the host is desired/mandatory, with a blanket rule saying |
| 24 |
> reference prefix unless it's a known exception, should be by /far/ the |
| 25 |
> easiest alternative, here. |
| 26 |
|
| 27 |
I think there's unfortunately no simple way to tell what should be in |
| 28 |
and what unfortunately has to be out. It depends a lot on the host |
| 29 |
system. I feel -- but I can't back this up with hard evidence -- that |
| 30 |
it are usually the libs that are not in *DEPEND that can only be |
| 31 |
available in the host system. Basically because they usually are part |
| 32 |
of the libc, which we assume to be installed. |
| 33 |
|
| 34 |
|
| 35 |
[1] http://dev.gentoo.org/~grobian/prefix-quiz |
| 36 |
|
| 37 |
-- |
| 38 |
Fabian Groffen |
| 39 |
Gentoo on a different level |
Archives