On 10/26/13 00:54, Ruud Koolen wrote:
> It's bikeshedding time.
> 
> The RAP project (prefix with libc) is now ready to start getting merged

> I propose "prefix-native" for rap as an alternative. Does anyone have any 
> good 
> ideas for classic prefix?

As you say "prefix with libc" above: Is it necessary to /split/ Prefix into $rap
and $classic, or would it also fit to have $rap to /supplement/ classic?

In case of the latter, I could think of:

profiles/base/make.defaults:
 USE_EXPAND_UNPREFIXED+=" PREFIX" # for backwards compat, or we get 
"prefix_prefix"
 USE_EXPAND_HIDDEN+=" PREFIX"
 USE_EXPAND_IMPLICIT+=" PREFIX"
 USE_EXPAND_VALUES_PREFIX="prefix prefix-libc"
And to help bug#473598 eventually:
 USE_EXPAND_VALUES_PREFIX+=" ${USE_EXPAND_VALUES_ARCH//*-*}" # the base-archs 
only

To distinguish between glibc/uclibc/etc, existing ELIBC could do.

For the profiles itself:
 profiles/default/linux/$arch/13.0/prefix and
 profiles/default/linux/$arch/13.0/prefix/glibc
 profiles/default/linux/$arch/13.0/prefix/uclibc
or even
 profiles/default/linux/$arch/13.0/prefix and
 profiles/default/linux/$arch/13.0/prefix/libc/glibc
 profiles/default/linux/$arch/13.0/prefix/libc/uclibc

My .02 $currency.

/haubi/

Reply via email to