| 1 |
On Fri, 03 Oct 2008 17:09:43 -0700 |
| 2 |
Zac Medico <zmedico@g.o> wrote: |
| 3 |
> In order to allow mixed EAPIs in the profiles, and to avoid having |
| 4 |
> to configure the EAPI in every single layer, each directory of the |
| 5 |
> profile stack should be able to either override or inherit the EAPI |
| 6 |
> value that may have been defined in a previous layer of the profile |
| 7 |
> stack. If no EAPI has been previously defined then it can be assumed |
| 8 |
> to be 0. |
| 9 |
|
| 10 |
That gets really confusing. Easier to just have an eapi file in every |
| 11 |
directory. |
| 12 |
|
| 13 |
Are we going to stick a file directly under profiles/ too? Some things |
| 14 |
in there are EAPI dependent... It'd have to stay at 0 for quite a long |
| 15 |
time, of course. |
| 16 |
|
| 17 |
-- |
| 18 |
Ciaran McCreesh |
Archives