From: Brian Harring <ferringb@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Cc: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: [gentoo-portage-dev] allow extra info to be echod on die
Date: Wed, 5 Oct 2005 13:47:09 -0500 [thread overview]
Message-ID: <20051005184709.GD7855@nightcrawler> (raw)
In-Reply-To: <20051005164801.GC7855@nightcrawler>
[-- Attachment #1: Type: text/plain, Size: 1252 bytes --]
Just an addendum to this... it went in, will be available in
2.0.51_rc4 and up.
If you want all registered death funcs to kick in,
EBUILD_DEATH_HOOKS="$EBUILD_DEATH_HOOKS the_name_of_your_func"
or if you want just your func to run
EBUILD_DEATH_HOOKS="the_name_of_your_func"
CC'ing gentoo-dev, since I'd expect some devs would be interested in
it.
~harring
On Wed, Oct 05, 2005 at 11:48:01AM -0500, Brian Harring wrote:
> On Wed, Oct 05, 2005 at 04:33:17PM +0000, Thomas Matthijs wrote:
> > Hi,
> >
> > I would really like a way to echo more information when a die happens so
> > the users can paste it in their bug report
> >
> > Only needs a very simple change to ebuild.sh:
> >
> EBUILD_DEATH_HOOKS=''
>
> 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
> }
> ^^^ something like that I think is a bit better; passing the diefunc
> args to the hooks also.
> ~harring
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next parent reply other threads:[~2005-10-05 18:52 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 ` Brian Harring [this message]
2005-10-05 18:55 ` [gentoo-dev] Re: [gentoo-portage-dev] allow extra info to be echod on die Daniel Ostrow
2005-10-05 19:04 ` Aron Griffis
2005-10-05 19:14 ` Brian Harring
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=20051005184709.GD7855@nightcrawler \
--to=ferringb@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=gentoo-portage-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