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