| 1 |
On Sat, 2009-02-21 at 18:55 -0500, Mike Frysinger wrote: |
| 2 |
> On Saturday 21 February 2009 18:38:55 Ryan Hill wrote: |
| 3 |
> > On Sat, 21 Feb 2009 18:27:10 -0500 Mike Frysinger wrote: |
| 4 |
> > > looks like bash-4.0 has broken semicolon escaping in subshells. this |
| 5 |
> > > comes up when using find's -exec like we do in a few places in |
| 6 |
> > > eclasses: ls=$(find "$1" -name '*.po' -exec basename {} .po \;); shift |
| 7 |
> > > you can work around the issue in a couple of ways: |
| 8 |
> > > - quote the semicolon: |
| 9 |
> > > .... ';') |
| 10 |
> > > - use backticks |
| 11 |
> > > `find .... \;` |
| 12 |
> > > |
| 13 |
> > > i'll tweak the eclasses to use quoting for now |
| 14 |
> > |
| 15 |
> > is this a bug or broken on purpose? |
| 16 |
> |
| 17 |
> i say it's a bug, but i'm not the bash maintainer |
| 18 |
> |
| 19 |
> i imagine it's fall out from attempts to fix support for case statements in |
| 20 |
> subshells |
| 21 |
|
| 22 |
Then the bug should be fixed, instead of changing usage to something |
| 23 |
apparently less common, as the conversion could miss some. And more |
| 24 |
importantly users still want to use \; for find -exec ending on their |
| 25 |
command line and their very own scripts. |
| 26 |
And who knows how many shell scripts shipped by packages use the |
| 27 |
escaping method. |
| 28 |
|
| 29 |
|
| 30 |
-- |
| 31 |
Mart Raudsepp |
| 32 |
Gentoo Developer |
| 33 |
Mail: leio@g.o |
| 34 |
Weblog: http://planet.gentoo.org/developers/leio |
Archives