From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org)
	by finch.gentoo.org with esmtp (Exim 4.60)
	(envelope-from <gentoo-dev+bounces-50123-garchives=archives.gentoo.org@lists.gentoo.org>)
	id 1S63xv-0003HP-HY
	for garchives@archives.gentoo.org; Fri, 09 Mar 2012 17:50:56 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id 7DE4FE09C1;
	Fri,  9 Mar 2012 17:50:46 +0000 (UTC)
Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183])
	by pigeon.gentoo.org (Postfix) with ESMTP id E6FB9E089D
	for <gentoo-dev@lists.gentoo.org>; Fri,  9 Mar 2012 17:50:19 +0000 (UTC)
Received: from pomiocik.lan (159-205-88-242.adsl.inetia.pl [159.205.88.242])
	(using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits))
	(No client certificate requested)
	(Authenticated sender: mgorny)
	by smtp.gentoo.org (Postfix) with ESMTPSA id 136CC1B403C;
	Fri,  9 Mar 2012 17:50:17 +0000 (UTC)
Date: Fri, 9 Mar 2012 18:52:40 +0100
From: =?UTF-8?B?TWljaGHFgiBHw7Nybnk=?= <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: michael@orlitzky.com
Subject: Re: [gentoo-dev] RFD: EAPI specification in ebuilds
Message-ID: <20120309185240.1ee1cb58@pomiocik.lan>
In-Reply-To: <4F5A3E6C.4040900@orlitzky.com>
References: <20311.51166.725757.212932@a1i15.kph.uni-mainz.de>
	<4F57DDB5.3090503@orlitzky.com>
	<20120308130310.69c3c714@pomiocik.lan>
	<4F58D6A5.7070804@orlitzky.com>
	<20120308182844.11201771@pomiocik.lan>
	<4F58F103.5010503@orlitzky.com>
	<20120308175345.2c4b72ff@googlemail.com>
	<4F58FC55.7070005@orlitzky.com>
	<20120308184820.108fc30c@googlemail.com>
	<4F592612.6050203@orlitzky.com>
	<20120309060424.09cdce1e@pomiocik.lan>
	<4F599692.9050503@orlitzky.com>
	<20120309172921.281ee5a0@pomiocik.lan>
	<4F5A368D.2020605@orlitzky.com>
	<20314.14772.897891.110368@a1i15.kph.uni-mainz.de>
	<4F5A3E6C.4040900@orlitzky.com>
Organization: Gentoo
X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; x86_64-pc-linux-gnu)
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@lists.gentoo.org
Reply-to: gentoo-dev@lists.gentoo.org
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=PGP-SHA256;
 boundary="Sig_/Jfq1+ta4R_/.GTsfkpmQfbm"; protocol="application/pgp-signature"
X-Archives-Salt: 833be038-7b2c-43b8-856d-401442e54ac9
X-Archives-Hash: afd9d22648df7e7b59f25bf821a33798

--Sig_/Jfq1+ta4R_/.GTsfkpmQfbm
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Fri, 09 Mar 2012 12:31:24 -0500
Michael Orlitzky <michael@orlitzky.com> wrote:

> On 03/09/12 12:11, Ulrich Mueller wrote:
> >>>>>> On Fri, 09 Mar 2012, Michael Orlitzky wrote:
> >=20
> >>> What if bash starts to parse the script completely and barfs at
> >>> 'syntax error' before it starts executing stuff?
> >=20
> >> It doesn't parse the script completely, it executes line-by-line,
> >> so we can bail out early.
> >=20
> > How can you tell that this behaviour won't be changed in a future
> > bash version?
> >=20
>=20
> Who's to say that in the future my computer won't be made out of
> delicious ice cream, eliminating the need for EAPIs entirely?
>=20
> Chances are, this would break thousands of scripts, so we hope they
> wouldn't do it. If it does happen, we either deal with it then, or
> don't upgrade to that version of bash -- the same as we would do with
> any other massive breaking change.

Thousands of scripts? So... you're saying that people actually use
thousands of scripts which have invalid syntax...

Well, one thing I can think of now is makeself and similar. Those are
indeed a quite good argument.

But the main point here is that at some point someone may want to use
a non-bash syntax for ebuilds. Or some kind of optional bash extension.

--=20
Best regards,
Micha=C5=82 G=C3=B3rny

--Sig_/Jfq1+ta4R_/.GTsfkpmQfbm
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)

iJwEAQEIAAYFAk9aQ2kACgkQfXuS5UK5QB1EOwP/ZwxsKOXgmUlaeCLBPuVoAXFW
70WvO+ack2N2ky5/kuZ3RmVeUwam526PyjS+SadKC5BYMJGJzgx1ZDR/8AqEbPMR
iftenqxqnko54ESGofR9xhJWspZlZLbxKsnEdLhJVW6lZ/ofSY8y/HLsVYAjmW3p
ht4q3U7PQPb/atgyf2c=
=qwYB
-----END PGP SIGNATURE-----

--Sig_/Jfq1+ta4R_/.GTsfkpmQfbm--