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] List of ebuild functions that die/do not die
Date: Wed, 24 Dec 2008 11:20:42 -0500	[thread overview]
Message-ID: <4952615A.40802@gentoo.org> (raw)
In-Reply-To: <8b4c83ad0812240813he864b06j452a4fe1fa2ffa33@mail.gmail.com>

Nirbheek Chauhan wrote:
> On Wed, Dec 24, 2008 at 8:27 PM, Thomas Sachau <tommy@gentoo.org> wrote:
>   
>> As it seems like noone else is doing something about it, i have started a list with some entries[1].
>> Please send me more functions and their place and error reports directly to me (via mail or irc).
>>     
>
> I thought that the rules for determination were pretty straightforward:
>
> commands that die:
> everything that is implemented as a function (ebuild.sh, eclasses, etc)
>
> commands that don't die:
> every external application (do*, cp, etc)
>
>
>   
Technically the rule is that eclasses shouldn't die. At least that's the 
latest version of the rules that I remember.



  reply	other threads:[~2008-12-24 16:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-24  5:58 [gentoo-dev] Re: what happened to /etc/init.d/hal{d,daemon,whatever} script ? Andrey Grozin
2008-12-24  6:19 ` Jeremy Olexa
2008-12-24 14:40   ` Ciaran McCreesh
2008-12-29 12:56   ` Ben de Groot
2009-01-09 14:00     ` [gentoo-dev] " Steve Long
2008-12-24 14:57 ` [gentoo-dev] List of ebuild functions that die/do not die Thomas Sachau
2008-12-24 16:13   ` Nirbheek Chauhan
2008-12-24 16:20     ` Doug Goldstein [this message]
2008-12-24 16:43       ` Nirbheek Chauhan
2008-12-24 17:18         ` [gentoo-dev] " Steve Long

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=4952615A.40802@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