| 1 |
On Fri, 10 Jan 2014 01:29:28 -0600 |
| 2 |
Donnie Berkholz <dberkholz@g.o> wrote: |
| 3 |
> (This involves setting EAPI=5 in the main profiles directory, then |
| 4 |
> moving the eapi-5-files files to a suitable place (base?) and |
| 5 |
> removing the eapi-5-files directory.) |
| 6 |
|
| 7 |
Just to be clear, quoting PMS, (especially the last sentence): |
| 8 |
|
| 9 |
> A profile directory may contain an \t{eapi} file. This file, if it |
| 10 |
> exists, must contain a single line with the name of an EAPI. This |
| 11 |
> specifies the EAPI to use when handling the directory in question; a |
| 12 |
> package manager must not attempt to use any profile using a directory |
| 13 |
> which requires an EAPI it does not support. If no \t{eapi} file is |
| 14 |
> present, EAPI 0 shall be used. The EAPI is not inherited via the |
| 15 |
> \t{parent} file. |
| 16 |
|
| 17 |
To avoid confusion, it's probably better to indiscriminately drop an |
| 18 |
EAPI 5 file in every single directory. |
| 19 |
|
| 20 |
-- |
| 21 |
Ciaran McCreesh |
Archives