| 1 |
-----BEGIN PGP SIGNED MESSAGE-----
|
| 2 |
Hash: SHA1
|
| 3 |
|
| 4 |
On Thu, 14 May 2009 16:49:09 -0500
|
| 5 |
William Hubbs <williamh@g.o> wrote:
|
| 6 |
> The second solution seems to be the better one because it does not go |
| 7 |
> against standards. For example, we see extentions like .c, .py and |
| 8 |
> .pl, instead of .c-43, .py-25 and .pl-58. There are ways within the |
| 9 |
> languages to tell which version of the compiler is compiling them as |
| 10 |
> needed. So, If we say that, EAPI 4, for example, requires bash-4.0, |
| 11 |
> Isn't there a way the PM could find out which version of bash is being |
| 12 |
> run, compare that to the EAPI, then take appropriate action? |
| 13 |
|
| 14 |
It can't, because it doesn't know the EAPI until it's sourced the thing
|
| 15 |
using bash. Using things like += in global scope will break older bash
|
| 16 |
versions to the point that they can't reliably extract EAPI.
|
| 17 |
|
| 18 |
- --
|
| 19 |
Ciaran McCreesh
|
| 20 |
-----BEGIN PGP SIGNATURE-----
|
| 21 |
Version: GnuPG v2.0.9 (GNU/Linux)
|
| 22 |
|
| 23 |
iEYEARECAAYFAkoMkuMACgkQ96zL6DUtXhEWmQCeOIHQLeguFo7vZXQCG5aE5imF
|
| 24 |
0rIAn1tOEyeyATdwoLGI8dCUs5s3afKR
|
| 25 |
=JRMB
|
| 26 |
-----END PGP SIGNATURE----- |
Archives