| 1 |
I have noticed that the arch profile directories (profiles/arch/$ARCH) |
| 2 |
are not EAPI 5 capable. These profiles are inherited by both the default |
| 3 |
and hardened profiles and contain arch-specific settings. They are often |
| 4 |
used to override masks set in the base profile. |
| 5 |
|
| 6 |
The base profile already has an EAPI 5 equivalent in profiles/eapi-5-files. |
| 7 |
|
| 8 |
I would like to add use.stable.mask to the arch profiles to avoid |
| 9 |
duplicating entries in profiles/default/linux/$ARCH/13.0/use.stable.mask |
| 10 |
and profiles/hardened/linux/$ARCH/use.stable.mask. This would make |
| 11 |
future stabilizations of dev-lang/python easier to coordinate. [1] |
| 12 |
|
| 13 |
Is it acceptable to just bump eapi to 5 in the existing arch profiles? |
| 14 |
This would render the default/linux/$ARCH/10.0 profiles unusable in old |
| 15 |
version of portage. |
| 16 |
|
| 17 |
Here are a couple of alternatives: |
| 18 |
|
| 19 |
1. Add profiles/eapi-5-files/$ARCH. |
| 20 |
2. Add profiles/$ARCH/eapi-5-files. |
| 21 |
|
| 22 |
In either case, the default (13.0) and hardened profiles would be |
| 23 |
adjusted to inherit these. |
| 24 |
|
| 25 |
Which option do we prefer? Is there a better option? |
| 26 |
|
| 27 |
[1] https://bugs.gentoo.org/show_bug.cgi?id=474128#c33 |
Archives