public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Petteri Räty" <betelgeuse@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 16:49:28 +0200	[thread overview]
Message-ID: <4950FA78.3080602@gentoo.org> (raw)
In-Reply-To: <495079D0.5060704@avtomatika.com>

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

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


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  parent reply	other threads:[~2008-12-23 14:49 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 [this message]
2008-12-23 20:39       ` Doug Goldstein
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=4950FA78.3080602@gentoo.org \
    --to=betelgeuse@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