| 1 |
On Thu, 14 May 2009 22:03:22 +0200 |
| 2 |
Ben de Groot <yngwin@g.o> wrote: |
| 3 |
|
| 4 |
> I concur that speaking for myself, I don't understand the issue. And |
| 5 |
> it looks like many others don't either. So if anyone wants to promote |
| 6 |
> this GLEP, their job is clear: make people understand what the issue |
| 7 |
> is here, and convince them it is actually an issue. (Examples, |
| 8 |
> scenarios usually work well, indeed a lot better than calling people |
| 9 |
> names.) |
| 10 |
|
| 11 |
We need a mechanism to be able to use newer bash-features in ebuilds. |
| 12 |
Preferably one that doesn't go "Wait a couple of years, hope |
| 13 |
everyone did X then Just Do it." We want one that goes like "Get a new |
| 14 |
EAPI approved with new minimum bash-version attached, start using cool |
| 15 |
stuff like ( Bash-4.0 ): |
| 16 |
|
| 17 |
shopt -s globstar |
| 18 |
for i in /usr/share/man/**/*remote* |
| 19 |
do |
| 20 |
stuff |
| 21 |
done |
| 22 |
|
| 23 |
Built-in find in bash, how do you like them bananas? :-) |
| 24 |
|
| 25 |
find equivalent would be, if you wanted the same level of space-safety: |
| 26 |
|
| 27 |
while read -r line |
| 28 |
do |
| 29 |
stuff |
| 30 |
done < <(find /usr/share/man -name '*remote*') |
| 31 |
|
| 32 |
Personally, I like the first version better. It would be cool if we |
| 33 |
could start using it sooner. GLEP-55 provides the "clean" solution, by |
| 34 |
just making the file name indicate what's inside. No need to parse, no |
| 35 |
nothing. Portage is currently testing a "first line with EAPI= |
| 36 |
determines EAPI" method. That's slightly less clean, but has the added |
| 37 |
benefit of not breaking anything that relies on .ebuild extension for |
| 38 |
ebuilds and I think it's not an unreasonable limitation on ebuilds to |
| 39 |
require EAPI= to be parseable by !bash. |
| 40 |
|
| 41 |
/loki_val |
Archives