From: | "Dawid Węgliński" <cla@g.o> | ||
---|---|---|---|
To: | gentoo-dev@l.g.o | ||
Subject: | Re: [gentoo-dev] bash-4.0 regression heads up (escaped semicolons in subshells) | ||
Date: | Sun, 22 Feb 2009 22:30:40 | ||
Message-Id: | 200902222330.09925.cla@gentoo.org | ||
In Reply to: | [gentoo-dev] bash-4.0 regression heads up (escaped semicolons in subshells) by Mike Frysinger |
1 | On Sunday 22 of February 2009 00:27:10 Mike Frysinger wrote: |
2 | > looks like bash-4.0 has broken semicolon escaping in subshells. this comes |
3 | > up when using find's -exec like we do in a few places in eclasses: |
4 | > ls=$(find "$1" -name '*.po' -exec basename {} .po \;); |
5 | > shift you can work around the issue in a couple of ways: |
6 | > - quote the semicolon: |
7 | > .... ';') |
8 | > - use backticks |
9 | > `find .... \;` |
10 | > |
11 | > i'll tweak the eclasses to use quoting for now |
12 | > -mike |
13 | |
14 | FYI. Not only find's semicolons are affected. It also happens in case ;; |
15 | construction. |
16 | |
17 | -- |
18 | Cheers, |
19 | Dawid Węgliński |
Subject | Author |
---|---|
Re: [gentoo-dev] bash-4.0 regression heads up (escaped semicolons in subshells) | Mike Frysinger <vapier@g.o> |