1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
Hi, |
5 |
|
6 |
I realize that I'm asking this very late in the discussion, so please |
7 |
bear with me if it has been hashed before. |
8 |
|
9 |
On Thu, May 14, 2009 at 11:16:23PM +0200, Peter Alfredsen wrote: |
10 |
> We need a mechanism to be able to use newer bash-features in ebuilds. |
11 |
> Preferably one that doesn't go "Wait a couple of years, hope |
12 |
> everyone did X then Just Do it." We want one that goes like "Get a new |
13 |
> EAPI approved with new minimum bash-version attached, start using cool |
14 |
> stuff like ( Bash-4.0 ): |
15 |
|
16 |
<snip> |
17 |
|
18 |
> Personally, I like the first version better. It would be cool if we |
19 |
> could start using it sooner. GLEP-55 provides the "clean" solution, by |
20 |
> just making the file name indicate what's inside. No need to parse, no |
21 |
> nothing. Portage is currently testing a "first line with EAPI= |
22 |
> determines EAPI" method. That's slightly less clean, but has the added |
23 |
> benefit of not breaking anything that relies on .ebuild extension for |
24 |
> ebuilds and I think it's not an unreasonable limitation on ebuilds to |
25 |
> require EAPI= to be parseable by !bash. |
26 |
|
27 |
I don't know how strong this argument is, but here is my opinion about |
28 |
the issue, followed up with a question. |
29 |
|
30 |
The second solution seems to be the better one because it does not go |
31 |
against standards. For example, we see extentions like .c, .py and |
32 |
.pl, instead of .c-43, .py-25 and .pl-58. There are ways within the |
33 |
languages to tell which version of the compiler is compiling them as |
34 |
needed. So, If we say that, EAPI 4, for example, requires bash-4.0, |
35 |
Isn't there a way the PM could find out which version of bash is being |
36 |
run, compare that to the EAPI, then take appropriate action? |
37 |
|
38 |
- -- |
39 |
William Hubbs |
40 |
gentoo accessibility team lead |
41 |
williamh@g.o |
42 |
-----BEGIN PGP SIGNATURE----- |
43 |
Version: GnuPG v2.0.11 (GNU/Linux) |
44 |
|
45 |
iEYEARECAAYFAkoMkdUACgkQblQW9DDEZTihowCdEynGXsB0Z1r9y43VeWEs9JLF |
46 |
SrQAn2iNPikCR+tZHGyrv+ykr4y1D+81 |
47 |
=6F5i |
48 |
-----END PGP SIGNATURE----- |