| 1 |
On 18:08 Fri 10 Jan , Ciaran McCreesh wrote: |
| 2 |
> On Fri, 10 Jan 2014 01:29:28 -0600 |
| 3 |
> Donnie Berkholz <dberkholz@g.o> wrote: |
| 4 |
> > A profile directory may contain an \t{eapi} file. This file, if it |
| 5 |
> > exists, must contain a single line with the name of an EAPI. This |
| 6 |
> > specifies the EAPI to use when handling the directory in question; a |
| 7 |
> > package manager must not attempt to use any profile using a |
| 8 |
> > directory which requires an EAPI it does not support. If no \t{eapi} |
| 9 |
> > file is present, EAPI 0 shall be used. The EAPI is not inherited via |
| 10 |
> > the \t{parent} file. |
| 11 |
> |
| 12 |
> To avoid confusion, it's probably better to indiscriminately drop an |
| 13 |
> EAPI 5 file in every single directory. |
| 14 |
|
| 15 |
Thanks Ciaran. Appreciate the clarification. |
| 16 |
|
| 17 |
-- |
| 18 |
Thanks, |
| 19 |
Donnie |
| 20 |
|
| 21 |
Donnie Berkholz |
| 22 |
Council Member / Sr. Developer, Gentoo Linux <http://dberkholz.com> |
| 23 |
Analyst, RedMonk <http://redmonk.com/dberkholz/> |
Archives