From: Mike Gardiner <obz@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] einfo / ewarn banners and die messages
Date: Fri, 12 Nov 2004 10:11:04 +0800 [thread overview]
Message-ID: <1100225464.8750.2.camel@localhost> (raw)
In-Reply-To: <20041112070757.GA21178@tiger.gg3.net>
On Fri, 2004-11-12 at 16:07 +0900, Georgi Georgiev wrote:
> maillog: 11/11/2004-22:02:30(-0800): Tuan Van types
> > And there are ebuilds that do*, in*, new* without die. The ebuild will
> > emerged successfully with the missing file(s).
> > Oh, who is glark?
>
> Shouldn't do*, in*, new* die on a failure?
>
I would concur, in what situations would we not want a do*, or new* to
not cause a build failure? Shouldn't functions always install something,
and not be used for any sort of 'if something exists, install it, or
else don't bother'?
Mike Gardiner
(Obz)
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-11-12 10:16 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 [this message]
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
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=1100225464.8750.2.camel@localhost \
--to=obz@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