From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Lb39T-0000ug-Fv for garchives@archives.gentoo.org; Sun, 22 Feb 2009 01:29:03 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 509E7E040D; Sun, 22 Feb 2009 01:29:02 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 142A5E040D for ; Sun, 22 Feb 2009 01:29:02 +0000 (UTC) Received: from vapier.localnet (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id 4457DB6869 for ; Sun, 22 Feb 2009 01:29:01 +0000 (UTC) From: Mike Frysinger Organization: wh0rd.org To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Re: bash-4.0 regression heads up (escaped semicolons in subshells) Date: Sat, 21 Feb 2009 20:28:59 -0500 User-Agent: KMail/1.11.0 (Linux/2.6.28; KDE/4.2.0; x86_64; ; ) References: <200902211827.10563.vapier@gentoo.org> <200902211944.35760.vapier@gentoo.org> <1235264091.23876.24.camel@localhost> In-Reply-To: <1235264091.23876.24.camel@localhost> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1311311.SqFQPIf3H5"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200902212029.00333.vapier@gentoo.org> X-Archives-Salt: 7767169c-8b5e-45a5-9306-ebb51aac5a3f X-Archives-Hash: 6d22583660289a14bb6d114f606a5d52 --nextPart1311311.SqFQPIf3H5 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Saturday 21 February 2009 19:54:51 Mart Raudsepp wrote: > On Sat, 2009-02-21 at 19:44 -0500, Mike Frysinger wrote: > > On Saturday 21 February 2009 19:38:33 Mart Raudsepp wrote: > > > On Sat, 2009-02-21 at 19:29 -0500, Mike Frysinger wrote: > > > > On Saturday 21 February 2009 19:00:19 Mart Raudsepp wrote: > > > > > On Sat, 2009-02-21 at 18:55 -0500, Mike Frysinger wrote: > > > > > > On Saturday 21 February 2009 18:38:55 Ryan Hill wrote: > > > > > > > On Sat, 21 Feb 2009 18:27:10 -0500 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=3D$(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 > > > > > > > > > > > > > > is this a bug or broken on purpose? > > > > > > > > > > > > i say it's a bug, but i'm not the bash maintainer > > > > > > > > > > > > i imagine it's fall out from attempts to fix support for case > > > > > > statements in subshells > > > > > > > > > > Then the bug should be fixed, instead of changing usage to > > > > > something apparently less common, as the conversion could miss > > > > > some. And more importantly users still want to use \; for find > > > > > -exec ending on their command line and their very own scripts. > > > > > And who knows how many shell scripts shipped by packages use the > > > > > escaping method. > > > > > > > > i think you missed the entire point of this thread: there's a bug in > > > > bash-4.0 that code is likely to hit. > > > > > > I think you missed the entire point of my reply. > > > That bug should be fixed, not workarounds applied all over the tree, = as > > > users still want to be able to escape semi-colons. > > > > no one suggested doing any of this crap you're talking about. if you > > want to get all retarded, dont install the masked ebuild. i gave a hea= ds > > up to people who might want to experiment so they wouldnt have to figure > > out weird errors. in the mean time, i tweaked a few common files so > > people wouldnt hit errors and could investigate even further. > > =EF=BB=BFPerhaps you should actually state those intentions at the start = instead > of starting to rant out on people replying. > Sounds good now that we actually know what the plan is. i guess i used too many code words like "bash-4.0 is broken" and "workaroun= d". =20 i'll address this in the future by just mailing base-system@gentoo.org as t= hey=20 should be familiar with these insider terms. =2Dmike --nextPart1311311.SqFQPIf3H5 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iQIcBAABAgAGBQJJoKpcAAoJEEFjO5/oN/WBf5oP/jLumxYXMaGN6OHxSH0TDiNE A8D7xuUfBwXFLvKoO4mrB7nPGzU/OO2Jo03cXD7BMKdToXPCOoGVsTPFtwIsouXK juFP1snsnmiNcjPS2++O/6bplRRkcN8E6s+ixGlHQopeptyaOJmeIz8rUKIpCexj EzDfs9QStnea1ncXU/1nPvUQXHinjtTG1OPjYPWLUI7VOBvlOKh6+KxoGW+FCqyi KYb7ZoN5Dhlm0Zm8wzg6OUi/GzdXMKECZSe2xaXZiVOPmejruJrDflw82cgpgu5O jqNUcLRbQhJ5vcsjWHgjkA3fINmCnRFSsSqd0i3NiXRy2cLOaCzZLoc/HHZlUl4y O6pSio4Y291mkCaQu7PrXEbJq8uDwQwvKwi5Bq64+SRf3/KdFGnI8nJ3zF7Q/Lke 2gMc/zXAwYz+ZQy4hKIYEQrJf1Fb1RnZ5Hzvrdd5/1JUJTJfBTxEZw9zEpNc4RK6 WGY+FFNE5H1W95DaQj4elGldVoJ81b02OIy0tTYCIuFKyEDpOkiDFXCurDqJu0iB QCkkwTd+IsUDgPs+kwnLFD69AHRACpmQWkN3rZ36F9YdNaX9b7SsR80SFcAKoauU H/yGC54Y2ZaD9dIEHu+LJ0Hv/l8yYY5cxhFK8NBKSw/S6sPXpVNTC0fD+HAZznwL Leifux1NzwIiOdeGz3S8 =f9ev -----END PGP SIGNATURE----- --nextPart1311311.SqFQPIf3H5--