public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Paul de Vrieze <pauldv@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] einfo / ewarn banners and die messages
Date: Mon, 15 Nov 2004 12:57:56 +0100	[thread overview]
Message-ID: <200411151257.57052.pauldv@gentoo.org> (raw)
In-Reply-To: <20041113144350.GA25074@tiger.gg3.net>

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

On Saturday 13 November 2004 15:43, Georgi Georgiev wrote:
> maillog: 13/11/2004-05:44:49(-0600): Matthew Kenendy types
>
> > Perhaps doins should take a --strict argument, whose absence will be
> > compatible with what I do now and whose presence will be appreciated
> > by those developers forgetting to install init.d run scripts etc.
>
> "--strict" v.s. "|| die"
>
> If this is the case, I'd say "|| die" is the more intuitive. Devs who
> forget will not appreciate --strict, because it doesn't make much of a
> difference if they had to add --strict or append "|| die".
>
> do* et al, should either always die, or be left as they are.
>
> In fact, a "--relaxed" option to those functions makes more sense.

I agree, even when files might be missing I surely want the packagers to 
know that. I've had some times when a new upstream tarbal did not contain 
a file anymore, while I was still installing it. If the do* functions had 
just died as to be expected, I would have caught the bug. Relying on 
developers never forgetting ||die is not a smart way to handle it.

Paul

-- 
Paul de Vrieze
Gentoo Developer
Mail: pauldv@gentoo.org
Homepage: http://www.devrieze.net

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

  reply	other threads:[~2004-11-15 11:58 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 [this message]
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=200411151257.57052.pauldv@gentoo.org \
    --to=pauldv@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