public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Doug Goldstein <cardoe@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev]  Re: what happened to /etc/init.d/hal{d,daemon,whatever} script ?
Date: Tue, 23 Dec 2008 15:39:53 -0500	[thread overview]
Message-ID: <49514C99.5020602@gentoo.org> (raw)
In-Reply-To: <4950FA78.3080602@gentoo.org>

Petteri Räty wrote:
> Branko Badrljica wrote:
>   
>> Since I might not be the only tinkerer on Gentoo to try stuff like that
>> and since it took me a day to find this, maybe it wouldn't hurt to check
>> for this kind of thing in portage ?
>> At the very least failed cp should stop emerge...
>>
>>
>>     
>
> Well there isn't a single place to add die statements. The important
> thing is for ebuild developers to remember to add || die to all stuff
> that could potentially fail. If you find the cp in question that failed
> for you, the right place to file bugs is https://bugs.gentoo.org.
>
> Regards,
> Petteri
>
>   
Looks like people have been truly over-zealous when removing "die" 
statements from ebuilds lately. I've added back to HAL an assortment of 
"die" statements.

I hope this hasn't happened in too many other ebuilds.



  reply	other threads:[~2008-12-23 20:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-22  4:18 [gentoo-dev] what happened to /etc/init.d/hal{d,daemon,whatever} script ? Branko Badrljica
2008-12-22  7:42 ` [gentoo-dev] " Duncan
2008-12-23  5:40   ` Branko Badrljica
2008-12-23  9:47     ` Robert R. Russell
2008-12-23 14:49     ` Petteri Räty
2008-12-23 20:39       ` Doug Goldstein [this message]
2008-12-23 22:21         ` Petteri Räty
2008-12-24 14:51         ` Daniel Pielmeier
  -- strict thread matches above, loose matches on Subject: below --
2008-12-24  5:58 Andrey Grozin
2008-12-24  6:19 ` Jeremy Olexa
2008-12-24 14:40   ` Ciaran McCreesh
2008-12-29 12:56   ` Ben de Groot

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=49514C99.5020602@gentoo.org \
    --to=cardoe@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