public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Aron Griffis <agriffis@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] einfo / ewarn banners and die messages
Date: Fri, 12 Nov 2004 10:22:02 -0500	[thread overview]
Message-ID: <20041112152202.GA452@time.flatmonk.org> (raw)
In-Reply-To: <20041112070757.GA21178@tiger.gg3.net>

[-- Attachment #1: Type: text/plain, Size: 1083 bytes --]

Georgi Georgiev wrote:	[Fri Nov 12 2004, 02:07:58AM EST]
> Shouldn't do*, in*, new* die on a failure?

I've flip-flopped on this one.  Previously I said that all dies should
be in the ebuild itself.  I even fixed a lot of ebuilds to call die
after said commands.  But I think that's a losing battle.  Nowadays I
agree that it would be easiest and best if econf, emake, do*, new*,
etc. would die on failure.  The simple reason is that there is no
situation in which one of these commands should fail normally in the
course of an ebuild.

The problem is that it isn't always possible.  Many of the commands
are implemented as scripts in /usr/lib/portage/bin instead of
functions so they can be used on the RHS of xargs.

One possibility would be to implement both: (1) functions in ebuild.sh
that would die automatically and (2) scripts in /usr/lib/portage/bin
that would operate on the RHS of xargs.  You'd lose the ability to die
automatically in the latter case, but hopefully it's rare enough that
it wouldn't be a big deal.

Regards,
Aron

--
Aron Griffis
Gentoo Linux Developer


[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]

  parent reply	other threads:[~2004-11-12 15:25 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-11 23:45 [gentoo-dev] einfo / ewarn banners and die messages Ciaran McCreesh
2004-11-12  6:02 ` Tuan Van
2004-11-12  7:07   ` Georgi Georgiev
2004-11-12  2:11     ` Mike Gardiner
2004-11-12 11:42       ` Aaron Walker
2004-11-12 15:30         ` Aron Griffis
2004-11-13  6:08           ` Matthew Kenendy
2004-11-12 23:07             ` Mike Gardiner
2004-11-13 11:44               ` Matthew Kenendy
2004-11-13 13:58                 ` Aron Griffis
2004-11-13 14:43                 ` Georgi Georgiev
2004-11-15 11:57                   ` Paul de Vrieze
2004-11-12 11:53       ` Thomas de Grenier de Latour
2004-11-12 15:22     ` Aron Griffis [this message]
2004-11-12 16:38     ` Tuan Van
2004-11-12  8:08   ` Ciaran McCreesh
2004-11-13 17:12 ` Tom Knight
2004-11-14 17:12   ` Ciaran McCreesh
2004-11-14 22:41     ` Aron Griffis
2004-11-14 22:47       ` 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=20041112152202.GA452@time.flatmonk.org \
    --to=agriffis@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