From: Peter Volkov <pva@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: fox.eclass update
Date: Thu, 16 Sep 2010 21:38:51 +0400 [thread overview]
Message-ID: <1284658731.14378.167.camel@tablet> (raw)
In-Reply-To: <20100916174400.0d878c9c@epia.jer-c2.orkz.net>
В Чтв, 16/09/2010 в 17:44 +0200, Jeroen Roovers пишет:
> On Thu, 16 Sep 2010 09:41:30 -0500
> Jeremy Olexa <darkside@gentoo.org> wrote:
>
> > * econf doesn't need to "|| die"
>
> 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.
--
Peter.
next prev parent reply other threads:[~2010-09-16 18:13 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-16 13:31 [gentoo-dev] RFC: fox.eclass update Matti Bickel
2010-09-16 13:39 ` Tomáš Chvátal
2010-09-16 14:24 ` Matti Bickel
2010-09-16 14:41 ` Jeremy Olexa
2010-09-16 15:44 ` Jeroen Roovers
2010-09-16 17:38 ` Peter Volkov [this message]
2010-09-16 16:48 ` Matti Bickel
2010-09-16 18:32 ` Peter Volkov
2010-09-16 18:51 ` Matti Bickel
2010-09-16 19:29 ` Mike Frysinger
2010-09-16 19:41 ` Peter Volkov
2010-09-16 22:34 ` Mike Frysinger
2010-09-17 3:51 ` [gentoo-dev] " Ryan Hill
2010-09-17 4:56 ` Mike Frysinger
2010-09-17 5:06 ` [gentoo-dev] " Peter Volkov
2010-09-17 5:24 ` Mike Frysinger
2010-09-16 20:24 ` Matti Bickel
2010-09-16 22:33 ` Mike Frysinger
2010-09-17 8:15 ` Michael Haubenwallner
-- strict thread matches above, loose matches on Subject: below --
2008-10-12 12:41 Matti Bickel
2008-10-13 10:56 ` Petteri Räty
2008-10-13 17:20 ` Donnie Berkholz
2008-10-13 18:28 ` Matti Bickel
2008-10-14 13:20 ` Bo Ørsted Andresen
2009-02-08 22:06 ` Matti Bickel
2009-02-09 15:01 ` Peter Volkov
2009-02-09 18:22 ` Matti Bickel
2009-02-10 5:10 ` Nirbheek Chauhan
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=1284658731.14378.167.camel@tablet \
--to=pva@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