| 1 |
On 04/27/2012 09:00 AM, Ciaran McCreesh wrote: |
| 2 |
> On Fri, 27 Apr 2012 08:55:49 -0700 |
| 3 |
> Zac Medico <zmedico@g.o> wrote: |
| 4 |
>> I suppose that we could do it both ways. The repoman check would be |
| 5 |
>> for people who want a practical approach that doesn't require all |
| 6 |
>> ebuilds to be converted to EAPI 5, and your strict die approach would |
| 7 |
>> be for people who want strictness and can afford to wait for the |
| 8 |
>> relevant ebuilds to be converted to EAPI 5. |
| 9 |
> |
| 10 |
> But there's no way the repoman check is going to give anything like |
| 11 |
> reliable answers if you're involving eclasses... |
| 12 |
|
| 13 |
Okay, so people who need "reliable answers" can go with your strict |
| 14 |
approach. Meanwhile, it's relatively easy to to a manual audit of the |
| 15 |
src_prepare function of each eclass. |
| 16 |
-- |
| 17 |
Thanks, |
| 18 |
Zac |
Archives