From: Jeremy Olexa <darkside@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: Wed, 24 Dec 2008 00:19:06 -0600 [thread overview]
Message-ID: <4951D45A.8030603@gentoo.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0812240553530.4080@woodpecker.gentoo.org>
Andrey Grozin wrote:
> On Wed, 24 Dec 2008, Petteri R?ty wrote:
>> Who has been removing die statements? Is this a suggested way of action
>> somewhere by someone?
> As recently discussed on the list, econf dies by itself, and || die
> should better be removed after econf. The same is true for, e.g.,
> eqmake4. It was discussed (don't have a reference to the thread at hand)
> that it would be useful to have a table which shows which functions die
> by themselves, and which not.
>
> Andrey
>
I see this asked every X months and never quite figured out why, (this
isn't personal against you, Andrey)
%% pwd
/usr/lib/portage/bin
%% grep -l die *
ebuild.sh
etc-update
isolated-functions.sh
misc-functions.sh
repoman
So, that means that none of these die:
%% ls do*
dobin* dodoc* dohard* doinitd* dolib.a* domo* dosed*
doconfd* doenvd* dohtml* doins* dolib.so* donewins@ dosym*
dodir* doexe* doinfo* dolib* doman* dosbin*
or
%% ls new*
newbin* newdoc* newexe* newins* newlib.so* newsbin*
newconfd* newenvd* newinitd* newlib.a* newman*
etc.
Take a look for yourself and you will see why there has never been a
"table" or anything created. (it is trivial - and you have the source on
your computer already)
Maybe this should be a question asked on the new dev quizies.."How do I
tell if something dies on its own or not?"
HTH,
Jeremy
next prev parent reply other threads:[~2008-12-24 6:19 UTC|newest]
Thread overview: 17+ 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 [this message]
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
2008-12-24 16:43 ` Nirbheek Chauhan
2008-12-24 17:18 ` [gentoo-dev] " Steve Long
-- strict thread matches above, loose matches on Subject: below --
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
2008-12-23 22:21 ` Petteri Räty
2008-12-24 14:51 ` Daniel Pielmeier
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=4951D45A.8030603@gentoo.org \
--to=darkside@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