| 1 |
On Sat, 21 Feb 2009 18:55:37 -0500 |
| 2 |
Mike Frysinger <vapier@g.o> wrote: |
| 3 |
|
| 4 |
> On Saturday 21 February 2009 18:38:55 Ryan Hill wrote: |
| 5 |
> > On Sat, 21 Feb 2009 18:27:10 -0500 Mike Frysinger wrote: |
| 6 |
> > > looks like bash-4.0 has broken semicolon escaping in subshells. |
| 7 |
> > > this comes up when using find's -exec like we do in a few places |
| 8 |
> > > in eclasses: ls=$(find "$1" -name '*.po' -exec basename {} .po |
| 9 |
> > > \;); shift you can work around the issue in a couple of ways: |
| 10 |
> > > - quote the semicolon: |
| 11 |
> > > .... ';') |
| 12 |
> > > - use backticks |
| 13 |
> > > `find .... \;` |
| 14 |
> > > |
| 15 |
> > > i'll tweak the eclasses to use quoting for now |
| 16 |
> > |
| 17 |
> > is this a bug or broken on purpose? |
| 18 |
> |
| 19 |
> i say it's a bug, but i'm not the bash maintainer |
| 20 |
> |
| 21 |
> i imagine it's fall out from attempts to fix support for case |
| 22 |
> statements in subshells |
| 23 |
|
| 24 |
thanks for the heads up. |
| 25 |
|
| 26 |
-- |
| 27 |
gcc-porting, by design, by neglect |
| 28 |
treecleaner, for a fact or just for effect |
| 29 |
wxwidgets @ gentoo EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662 |
Archives