| 1 |
On Sat, Aug 2, 2008 at 12:26 PM, Zac Medico <zmedico@g.o> wrote: |
| 2 |
> Mike Auty wrote: |
| 3 |
> |
| 4 |
>> If there's need for a new class of ebuild information (such as a new |
| 5 |
>> way of categorizing ebuilds by feature), perhaps we should add an ebuild |
| 6 |
>> features variable specifically for the purpose? |
| 7 |
> |
| 8 |
> That requires an EAPI bump, which also means that it can't be used |
| 9 |
> in ebuilds with EAPI 0 or 1. The RESTRICT solution is simpler and we |
| 10 |
> can use it right now in any ebuild. |
| 11 |
> |
| 12 |
|
| 13 |
I don't think we're in a hurry for this feature, so I don't see the |
| 14 |
need of using suboptimal hacks in order to avoid an EAPI bump. |
| 15 |
Furthermore, EAPI 2 is supposed to be done in the near future, right? |
| 16 |
|
| 17 |
Regards, |
| 18 |
-- |
| 19 |
Santiago M. Mola |
| 20 |
Jabber ID: cooldwind@×××××.com |
Archives