From: Brian Harring <ferringb@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-portage-dev] allow extra info to be echod on die
Date: Wed, 5 Oct 2005 14:14:57 -0500 [thread overview]
Message-ID: <20051005191457.GA10159@nightcrawler> (raw)
In-Reply-To: <20051005190423.GG28593@olive.flatmonk>
[-- Attachment #1: Type: text/plain, Size: 1033 bytes --]
On Wed, Oct 05, 2005 at 03:04:23PM -0400, Aron Griffis wrote:
> Brian Harring wrote: [Wed Oct 05 2005, 02:47:09PM EDT]
> >> diefunc() {
> >> local funcname="$1" lineno="$2" exitcode="$3"
> >> shift 3
> >> @@ -289,6 +291,7 @@
> >> echo "!!! ${*:-(no error message)}" >&2
> >> echo "!!! If you need support, post the topmost build error, NOT
> >this status message." >&2
> >> echo >&2
> >> + for x in $EBUILD_DEATH_HOOKS; do
> >> + ${x} "$1" "$2" "$3"
> >> + done
> >> exit 1
> >> }
>
> Is this exactly what went in? It looks like you're trying to use
> positional params that were shifted earlier.
No, the hooks are called with "$@" actually, plus some checks to
ensure that
A) the output goes to stderr, which is the norm for die
B) the hooks aren't engaged during depends phase.
if people are after the func/line/exit code being handed to the hook,
it can be changed, the intention was for this to allow dumping extra
debug info.
~harring
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-10-05 19:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20051005163317.GA6783@toucan.gentoo.org>
[not found] ` <20051005164801.GC7855@nightcrawler>
2005-10-05 18:47 ` [gentoo-dev] Re: [gentoo-portage-dev] allow extra info to be echod on die Brian Harring
2005-10-05 18:55 ` Daniel Ostrow
2005-10-05 19:04 ` Aron Griffis
2005-10-05 19:14 ` Brian Harring [this message]
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=20051005191457.GA10159@nightcrawler \
--to=ferringb@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