| 1 |
On Thu, Feb 26, 2009 at 11:50 PM, Ciaran McCreesh |
| 2 |
<ciaran.mccreesh@××××××××××.com> wrote: |
| 3 |
> On Thu, 26 Feb 2009 18:07:32 +0000 |
| 4 |
> Ciaran McCreesh <ciaran.mccreesh@××××××××××.com> wrote: |
| 5 |
>> There's a less extreme variant on this that's slightly cleaner, and |
| 6 |
>> with appropriate weaseling is also less messy. Simply add the |
| 7 |
>> following very carefully worded additional requirement for future |
| 8 |
>> EAPIs, and retroactively impose it upon current ones: |
| 9 |
>> |
| 10 |
>> If EAPI is to be set, it must be set strictly before any global scope |
| 11 |
>> command or package manager defined function is called. Once set, EAPI |
| 12 |
>> must not be set to a different value. |
| 13 |
> |
| 14 |
> ...not quite weasely enough. Also needs: |
| 15 |
> |
| 16 |
> and before any package manager defined variables are used or package |
| 17 |
> manager set shell behaviour is relied upon. |
| 18 |
> |
| 19 |
|
| 20 |
Is the following a stricter subset of your wording? -- |
| 21 |
|
| 22 |
"EAPI must be set in an ebuild as the first non-comment line, and |
| 23 |
thereafter must not be set to a different value" |
| 24 |
|
| 25 |
I'm asking because it would be simpler for users and devs to |
| 26 |
understand, even if it is a subset. |
| 27 |
|
| 28 |
|
| 29 |
-- |
| 30 |
~Nirbheek Chauhan |
Archives