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-42598-garchives=archives.gentoo.org@lists.gentoo.org>)
	id 1OwIxP-0005UB-6b
	for garchives@archives.gentoo.org; Thu, 16 Sep 2010 18:13:15 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id CDAF9E07FD
	for <garchives@archives.gentoo.org>; Thu, 16 Sep 2010 18:13:14 +0000 (UTC)
Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183])
	by pigeon.gentoo.org (Postfix) with ESMTP id 60414E07F1
	for <gentoo-dev@lists.gentoo.org>; Thu, 16 Sep 2010 17:40:47 +0000 (UTC)
Received: from [192.168.1.35] (unknown [94.158.169.15])
	(using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits))
	(No client certificate requested)
	by smtp.gentoo.org (Postfix) with ESMTPSA id 56ABC1B4071
	for <gentoo-dev@lists.gentoo.org>; Thu, 16 Sep 2010 17:40:46 +0000 (UTC)
Subject: Re: [gentoo-dev] RFC: fox.eclass update
From: Peter Volkov <pva@gentoo.org>
To: gentoo-dev@lists.gentoo.org
In-Reply-To: <20100916174400.0d878c9c@epia.jer-c2.orkz.net>
References: <4C921C29.6010502@gentoo.org> <4C922892.6040500@gentoo.org>
	 <31eb09dd433b2a4a9b9a428a262db089@webmail.jolexa.net>
	 <20100916174400.0d878c9c@epia.jer-c2.orkz.net>
Content-Type: text/plain; charset="UTF-8"
Date: Thu, 16 Sep 2010 21:38:51 +0400
Message-ID: <1284658731.14378.167.camel@tablet>
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
X-Mailer: Evolution 2.30.3 
Content-Transfer-Encoding: quoted-printable
X-Archives-Salt: cc42fc11-081c-46aa-b407-888c3a5e8bbc
X-Archives-Hash: 6e9b00ef17f07d87ccbe45a753319cfb

=D0=92 =D0=A7=D1=82=D0=B2, 16/09/2010 =D0=B2 17:44 +0200, Jeroen Roovers =
=D0=BF=D0=B8=D1=88=D0=B5=D1=82:
> On Thu, 16 Sep 2010 09:41:30 -0500
> Jeremy Olexa <darkside@gentoo.org> wrote:
>=20
> > * econf doesn't need to "|| die"
>=20
> Is that a novelty change? Most of the tree still does econf || die ...

econf is function that dies on its own.

But still there is one case where || die after econf can be useful -
very-very long list of econf options you have to edit rather frequently.

econf \
	parameter1 \
	parameter2 \
	... \
	parameterN || die

In case || die is absent and developer forgot '\' at the end of line
portage will not abort build: econf with shortened list of options will
succeed and next most probably absent command `parameterk parameter$((k
+1)) ... parameterN` will have no || die at the end. In general case ||
die after econf is redundant and should be dropped.

--=20
Peter.