[gentoo-dev] List of ebuild functions that die/do not die
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). [1]: http://dev.gentoo.org/~tommy/ebuild-functions.txt -- Thomas Sachau Gentoo Linux Developer signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] List of ebuild functions that die/do not die
On Wed, Dec 24, 2008 at 8:27 PM, Thomas Sachau to...@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) -- ~Nirbheek Chauhan
Re: [gentoo-dev] List of ebuild functions that die/do not die
Nirbheek Chauhan wrote: On Wed, Dec 24, 2008 at 8:27 PM, Thomas Sachau to...@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.
Re: [gentoo-dev] List of ebuild functions that die/do not die
On Wed, Dec 24, 2008 at 9:50 PM, Doug Goldstein car...@gentoo.org wrote: Nirbheek Chauhan wrote: [snip] commands that die: everything that is implemented as a function (ebuild.sh, eclasses, etc) [snip] Technically the rule is that eclasses shouldn't die. At least that's the latest version of the rules that I remember. eclasses shouldn't die or functions inside eclasses shouldn't die? I meant the latter: s/(ebuild.sh/(inside ebuild.sh/ -- ~Nirbheek Chauhan