-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sat, May 16, 2009 at 01:11:34PM +0200, Ben de Groot wrote: > David Leverton wrote: > > But the point isn't that we want to be able to do those things. The point > > is > > that if the EAPI is in the filename, it's blatantly obvious that it has to > > be > > static, but adding strange and unintuitive restrictions on which shell > > constructs can be used is, well, strange and unintuitive. > > Except that we aren't talking about strange and unintuitive. All we are > saying is basically documenting current usage: put a line with EAPI= > near the top. That's very straighforward and intuitive. Plus, it works.
Agreed. The way I have always usedEAPI is, you set it once at the top of the EBUILD and you are done with it. As far as I know, there is no reason to change EAPI once it is set, and eclasses shouldn't be changing it. - -- William Hubbs gentoo accessibility team lead willi...@gentoo.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (GNU/Linux) iEYEARECAAYFAkoPAX8ACgkQblQW9DDEZTizJACfarJ8hZh4WQ7GC0kuraqTba9u FhkAn29jolc1O5D/jMWWA6TJaJcUZtbQ =529O -----END PGP SIGNATURE-----