PROFILE_ARCH is currently used for various sub-architectures (e.g. sparc32 vs sparc64, 32 bit ppc vs ppc64, xbox vs normal x86) that don't have their own keyword but that do occasionally need special behaviour. It can be used in conditionals, but because no-one ever quite got around to it, it *can't* legally be used to alter metadata.
Is there any particular reason PROFILE_ARCH shouldn't be added to USE_EXPAND? One example of something that could be fixed this way is sys-apps/s390-oco (bug #99255). There're various others too, most of which are in the "different upstream-provided binaries for different subarchs" category but there's the odd dep here and there too (e.g. on some multi ABI archs, certain kernel-related packages should dep upon a special compiler). The original idea was that PROFILE_ARCH would get expanded in a special way, like ARCH does, but it never got implemented. Doing things that way could still be an option, but expand seems to be the cleaner solution now. -- Ciaran McCreesh : Gentoo Developer (Wearer of the shiny hat) Mail : ciaranm at gentoo.org Web : http://dev.gentoo.org/~ciaranm
signature.asc
Description: PGP signature
