From: Stephen Bennett <spb@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Nested die error
Date: Thu, 14 Apr 2005 22:54:11 +0100 [thread overview]
Message-ID: <1113515651.18201.2.camel@localhost> (raw)
In-Reply-To: <200504141642.22339.caleb@gentoo.org>
On Thu, 2005-04-14 at 16:42 -0500, Caleb Tennis wrote:
> So it seems repoman doesn't like nested die calls like this:
>
> use blah && ( emake foo || die )
>
Yep, because that doesn't work.
> What's the trick? Wrap the emake in a if/then call?
Yes.
> Ignore repoman at the
> risk of potential finger breakage by mr_bones'?
Well, you can as long as you don't mind your ebuild not working. :)
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-04-14 21:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-14 21:42 [gentoo-dev] Nested die error Caleb Tennis
2005-04-14 21:50 ` Stefan Schweizer
2005-04-14 23:56 ` [gentoo-dev] " Michael Sterrett -Mr. Bones.-
2005-04-14 21:54 ` Stephen Bennett [this message]
2005-04-14 21:58 ` [gentoo-dev] " Caleb Tennis
2005-04-15 3:17 ` Mike Frysinger
2005-04-14 21:57 ` Olivier Crête
2005-04-15 3:20 ` Mike Frysinger
2005-04-14 21:59 ` Ciaran McCreesh
2005-04-14 22:05 ` Vibhav Garg
2005-04-14 22:11 ` Ciaran McCreesh
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=1113515651.18201.2.camel@localhost \
--to=spb@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