| 1 |
On 04/27/2012 08:45 AM, Ciaran McCreesh wrote: |
| 2 |
> On Fri, 27 Apr 2012 08:41:35 -0700 |
| 3 |
> Zac Medico <zmedico@g.o> wrote: |
| 4 |
>>> In order to make it globally available, you put it in EAPI 5, and |
| 5 |
>>> make the package mangler die at pretend time if the user has patches |
| 6 |
>>> specified for a package that isn't EAPI 5. |
| 7 |
>> |
| 8 |
>> Or, have repoman assert that src_prepare contains an epatch_user call |
| 9 |
>> if EAPI is less than 5. |
| 10 |
> |
| 11 |
> Why bother? That's hideously error prone. We have a simple way that's |
| 12 |
> guaranteed to work, and that is able to inform the user if their |
| 13 |
> expectations can't be met. |
| 14 |
|
| 15 |
I suppose that we could do it both ways. The repoman check would be for |
| 16 |
people who want a practical approach that doesn't require all ebuilds to |
| 17 |
be converted to EAPI 5, and your strict die approach would be for people |
| 18 |
who want strictness and can afford to wait for the relevant ebuilds to |
| 19 |
be converted to EAPI 5. |
| 20 |
-- |
| 21 |
Thanks, |
| 22 |
Zac |
Archives