| 1 |
On 10/29/2013 11:02 PM, Ruud Koolen wrote: |
| 2 |
> On Tuesday 29 October 2013 08:40:59 Michael Haubenwallner wrote: |
| 3 |
>> On 10/26/13 00:54, Ruud Koolen wrote: |
| 4 |
>>> It's bikeshedding time. |
| 5 |
>>> |
| 6 |
>>> The RAP project (prefix with libc) is now ready to start getting merged |
| 7 |
>>> |
| 8 |
>>> I propose "prefix-native" for rap as an alternative. Does anyone have any |
| 9 |
>>> good ideas for classic prefix? |
| 10 |
|
| 11 |
Actually 've read "prefix-native" to be the original Prefix without libc, |
| 12 |
that is using the "native" libc, and have "prefix-libc" for RAP. |
| 13 |
|
| 14 |
>> As you say "prefix with libc" above: Is it necessary to /split/ Prefix into |
| 15 |
>> $rap and $classic, or would it also fit to have $rap to /supplement/ |
| 16 |
>> classic? |
| 17 |
> |
| 18 |
> In what sense? On the profile level, we factor out the common base shared |
| 19 |
> between classic and rap (which is about 50%-75% of the existing profile), and |
| 20 |
> have both variants inherit this base (neither can inherit the other |
| 21 |
> directly). |
| 22 |
|
| 23 |
Have thought one inheriting the other is possible, but OK with me if not. |
| 24 |
|
| 25 |
> As for USE flags, the primary function of the new use flags is to |
| 26 |
> disable certain hacks in rap. Writing those as `if use prefix && ! use |
| 27 |
> prefix-libc` is not a nice situation, so we need both new flags. |
| 28 |
> |
| 29 |
> We keep USE=prefix, of course. The vast majority of cases of prefix support in |
| 30 |
> ebuilds applies equally to classic and rap; those will keep using `if use |
| 31 |
> prefix`. The new flags are solely for the handful of ebuilds that need to |
| 32 |
> distinguish between the variants. |
| 33 |
|
| 34 |
Trying to be conservative with new USE flags (along Jeremy's comment): |
| 35 |
|
| 36 |
Any real counts already for the "handful of ebuilds" to benefit from having |
| 37 |
"prefix-native" in addition to "prefix-libc" USE-flag? |
| 38 |
|
| 39 |
>> In case of the latter, I could think of: |
| 40 |
>> |
| 41 |
>> profiles/base/make.defaults: |
| 42 |
>> USE_EXPAND_UNPREFIXED+=" PREFIX" # for backwards compat, or we get |
| 43 |
>> "prefix_prefix" USE_EXPAND_HIDDEN+=" PREFIX" |
| 44 |
>> USE_EXPAND_IMPLICIT+=" PREFIX" |
| 45 |
>> USE_EXPAND_VALUES_PREFIX="prefix prefix-libc" |
| 46 |
>> And to help bug#473598 eventually: |
| 47 |
>> USE_EXPAND_VALUES_PREFIX+=" ${USE_EXPAND_VALUES_ARCH//*-*}" # the |
| 48 |
>> base-archs only |
| 49 |
> |
| 50 |
> I don't think I understand this. |
| 51 |
|
| 52 |
Just a proposed implementation detail, without having tried out. |
| 53 |
|
| 54 |
/haubi/ |
Archives