public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Thomas de Grenier de Latour <degrenier@easyconnect.fr>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] einfo / ewarn banners and die messages
Date: Fri, 12 Nov 2004 12:53:15 +0100	[thread overview]
Message-ID: <20041112125315.252953d8.degrenier@easyconnect.fr> (raw)
In-Reply-To: <1100225464.8750.2.camel@localhost>

On Fri, 12 Nov 2004 10:11:04 +0800
Mike Gardiner <obz@gentoo.org> wrote:

> in what situations would we not want a do*, or new* to not cause
> a build failure?

In eclasses. I think there are several which make things like
"dodoc README INSTALL COPYRIGHT" without testing if the files
actually exist. But that's easily fixable.

-- 
TGL.

--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2004-11-12 11:53 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 [this message]
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=20041112125315.252953d8.degrenier@easyconnect.fr \
    --to=degrenier@easyconnect.fr \
    --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