On Sunday 22 February 2009 17:30:09 Dawid Węgliński wrote:
> On Sunday 22 of February 2009 00:27:10 Mike Frysinger wrote:
> > looks like bash-4.0 has broken semicolon escaping in subshells. this
> > comes up when using find's -exec like we do in a few places in eclasses:
> > ls=$(find "$1" -name '*.po' -exec basename {} .po \;); shift you can work
> > around the issue in a couple of ways:
> > - quote the semicolon:
> > .... ';')
> > - use backticks
> > `find .... \;`
> >
> > i'll tweak the eclasses to use quoting for now
>
> FYI. Not only find's semicolons are affected. It also happens in case ;;
> construction.embedded case statements in $(...) subshells have always been broken. bash-4.0 is supposed to fix that. if you have some code that is broken, please post it so i can push it upstream. -mike
signature.asc
Description: This is a digitally signed message part.
