Note: Due to technical difficulties, the Archives are currently not up to date.
GMANE provides an alternative service for most mailing lists. c.f. bug 424647
On Thu, 08 Mar 2012 08:30:57 -0800
Zac Medico <zmedico@g.o> wrote:
> On 03/08/2012 01:42 AM, Marc Schiffbauer wrote:
> > * Ulrich Mueller schrieb am 08.03.12 um 08:27 Uhr:
> >> Such constructs also cannot be used with any of the other proposed
> >> solutions. And in fact, nobody is using such things in practice.
> >> _All_ ebuilds in the Portage tree can be successfully parsed with
> >> the regexp proposed.
> >
> > Ebuilds are bash scripts. I think introducing exceptions or
> > constraints here is not straightforward.
>
> Given that ebuilds already have to conform to a vast number of
> constraints that ordinary bash scripts do not. I think that it's
> perfectly reasonable for ebuilds to have a constrained syntax for
> EAPI assignments.
...and only EAPI assignments? Not for any other metadata variable?
Doesn't that sort of suggest that EAPI shouldn't be a metadata variable?
--
Ciaran McCreesh
|
|
