It's bikeshedding time. The RAP project (prefix with libc) is now ready to start getting merged into gx86 and (if necessary) prefix overlay, thus giving it some form of official status. Part of that job is writing new profiles for RAP, and adding USE flags allowing ebuilds to distinguish between the two variants of prefix: classic, and RAP. For both purposes, we need names for the two variants, and preferably clear and descriptive names too.
For the profiles, the plan is to add profiles default/linux/$arch/13.0/prefix/$classic and default/linux/$arch/13.0/prefix/$rap, possibly with one of the two variants being default and thus renamed to default/linux/$arch/13.0/prefix; default/linux/$arch/13.0/prefix/$classic would symlink to prefix/linux/$arch, or vice versa, and default/linux/$arch/13.0/prefix/$rap would be the all-new RAP profile. (They will probably have a considerable amount of shared structure factored out, but that's another matter.) For the USE flags, there are a handful of ebuilds that need to distinguish between prefix classic and prefix RAP: the toolchains work differently, and the fact that RAP doesn't have /usr/include, /lib, and /usr/lib as valid search paths causes complications for some packages. To support this, the plan is to introduce two new global USE flags, prefix-$classic and prefix-$rap, both of which are masked in the base profile and selectively unmasked in the different prefix profiles. For both purposes, we need names for the two variants. The names should have the property that their meaning should be reasonably clear to the uninitiated, not too ugly, and somewhat accurately describe the difference between the two versions. Specifically, reading the two profile names should give you a good indication of which one to choose, and seeing `if use prefix-$classic` in an ebuild should give the reader a fairly good idea of what's going on. During development, we've been using the name "prefix-rpath" for classic, and "prefix-libc" and "rap" for rap. Of those, I think prefix-rpath is acceptable, but could be improved; the other two are just bad, as far as I'm concerned, and should be replaced. I propose "prefix-native" for rap as an alternative. Does anyone have any good ideas for classic prefix? -- Ruud
