| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Hi everyone, |
| 5 |
|
| 6 |
Please consider a new "eapi" profile configuration file that will |
| 7 |
designate the EAPI to which any package atoms within a given layer |
| 8 |
of the profile stack must conform. This will allow package managers |
| 9 |
to bail out with an informative error message if the user |
| 10 |
accidentally selects a profile containing an EAPI that is not |
| 11 |
supported by the currently installed package manager. |
| 12 |
|
| 13 |
In order to allow mixed EAPIs in the profiles, and to avoid having |
| 14 |
to configure the EAPI in every single layer, each directory of the |
| 15 |
profile stack should be able to either override or inherit the EAPI |
| 16 |
value that may have been defined in a previous layer of the profile |
| 17 |
stack. If no EAPI has been previously defined then it can be assumed |
| 18 |
to be 0. |
| 19 |
|
| 20 |
The format of the configuration file can be very simple, containing |
| 21 |
only the EAPI value and nothing more. For example, a file containing |
| 22 |
just a single "0" character, followed by a newline, could be |
| 23 |
created at profiles/base/eapi in order to explicitly declare that |
| 24 |
atoms in the base profile conform to EAPI 0. However, this |
| 25 |
particular declaration would be redundant since the base profile |
| 26 |
does not inherit from any other profile and therefore it's EAPI |
| 27 |
would be assumed to be 0 anyway. |
| 28 |
|
| 29 |
Does this seem like a good approach? Are there any suggestions for |
| 30 |
improvements or alternative approaches? |
| 31 |
- -- |
| 32 |
Thanks, |
| 33 |
Zac |
| 34 |
-----BEGIN PGP SIGNATURE----- |
| 35 |
Version: GnuPG v2.0.9 (GNU/Linux) |
| 36 |
|
| 37 |
iEYEARECAAYFAkjmtEYACgkQ/ejvha5XGaNtSQCfXb2OQAYCEAe0Uuuu7Ou+DxyV |
| 38 |
QZsAn0VpUbKqHJP0XRZSg6mhFKeUNXui |
| 39 |
=qR8c |
| 40 |
-----END PGP SIGNATURE----- |
Archives