From: Ryan Hill <dirtyepic@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: bash-4.0 regression heads up (escaped semicolons in subshells)
Date: Sat, 21 Feb 2009 17:38:55 -0600 [thread overview]
Message-ID: <20090221173855.404ebed9@halo.dirtyepic.sk.ca> (raw)
In-Reply-To: 200902211827.10563.vapier@gentoo.org
[-- Attachment #1: Type: text/plain, Size: 761 bytes --]
On Sat, 21 Feb 2009 18:27:10 -0500
Mike Frysinger <vapier@gentoo.org> 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
> -mike
>
is this a bug or broken on purpose?
--
gcc-porting, by design, by neglect
treecleaner, for a fact or just for effect
wxwidgets @ gentoo EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-02-21 23:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-21 23:27 [gentoo-dev] bash-4.0 regression heads up (escaped semicolons in subshells) Mike Frysinger
2009-02-21 23:38 ` Ryan Hill [this message]
2009-02-21 23:55 ` [gentoo-dev] " Mike Frysinger
2009-02-22 0:00 ` Mart Raudsepp
2009-02-22 0:29 ` Mike Frysinger
2009-02-22 0:38 ` Mart Raudsepp
2009-02-22 0:44 ` Mike Frysinger
2009-02-22 0:54 ` Mart Raudsepp
2009-02-22 1:28 ` Mike Frysinger
2009-02-22 7:40 ` Nirbheek Chauhan
2009-02-24 15:52 ` Daniel Gryniewicz
2009-02-24 15:56 ` Mike Frysinger
2009-02-22 1:02 ` Ryan Hill
2009-02-22 22:30 ` [gentoo-dev] " Dawid Węgliński
2009-02-22 22:39 ` Mike Frysinger
2009-02-22 23:03 ` Dawid Węgliński
2009-02-23 0:00 ` Mike Frysinger
2009-02-24 4:16 ` Mike Frysinger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090221173855.404ebed9@halo.dirtyepic.sk.ca \
--to=dirtyepic@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox