-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, 14 May 2009 16:49:09 -0500
William Hubbs <williamh@g.o> wrote:
> The second solution seems to be the better one because it does not go
> against standards.  For example, we see extentions like .c, .py and
> .pl, instead of .c-43, .py-25 and .pl-58.  There are ways within the
> languages to tell which version of the compiler is compiling them as
> needed.  So, If we say that, EAPI 4, for example, requires bash-4.0,
> Isn't there a way the PM could find out which version of bash is being
> run, compare that to the EAPI, then take appropriate action?

It can't, because it doesn't know the EAPI until it's sourced the thing
using bash. Using things like += in global scope will break older bash
versions to the point that they can't reliably extract EAPI.

- -- 
Ciaran McCreesh
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEARECAAYFAkoMkuMACgkQ96zL6DUtXhEWmQCeOIHQLeguFo7vZXQCG5aE5imF
0rIAn1tOEyeyATdwoLGI8dCUs5s3afKR
=JRMB
-----END PGP SIGNATURE-----