| 1 |
Ohai, |
| 2 |
|
| 3 |
As part of the RAP project[1], a version of Gentoo Prefix that uses its own |
| 4 |
libc rather than relying on the host version, prefix needs some new profiles |
| 5 |
serving this variant. While this is entirely inconsequential for most |
| 6 |
packages, there are a handful of ebuilds that need to distinguish between the |
| 7 |
two prefix variants. |
| 8 |
|
| 9 |
The chief difference between the two variants from the point of view of |
| 10 |
ebuilds is that in classic prefix, the host /usr/include is a valid include |
| 11 |
path (as it contains libc headers), whereas in RAP prefix it is not, and |
| 12 |
analogously so for library paths; this needs special handling for packages |
| 13 |
with build scripts that do their own exiting custom library searching, such |
| 14 |
as python, which needs to do certain prefix-specific hacks only for classic |
| 15 |
prefix and not for RAP. |
| 16 |
|
| 17 |
To this end, I'm introducing a globally masked USE flag, "prefix-guest", which |
| 18 |
is masked in the base profile and unmasked and forced in some prefix |
| 19 |
profiles; this flag indicates that /usr/include, /lib, and /usr/lib are valid |
| 20 |
paths despite being on a prefix system. This flag will be on in classic |
| 21 |
prefix, and off in prefix RAP. |
| 22 |
|
| 23 |
I will proceed in a week, assuming no complaints arise. |
| 24 |
|
| 25 |
-- Ruud |
| 26 |
|
| 27 |
[1] |
| 28 |
http://blogs.gentoo.org/news/2013/11/01/gentoo-monthly-newsletter-31-october-2013/#RAP |
Archives