Re: [gentoo-dev] Usage of econf with an additional || die

[Thomas Sachau <tommy@gentoo.org>]

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

Jeremy Olexa schrieb:
> Ben de Groot wrote:
> 
>> So, can we have a nice little table of which functions die by themselves
>> and which ones need || die added in ebuilds? Please?
>>
>> Thanks,
>>
> 
> A quick grep of /usr/lib/portage/bin clues you in that every function
> that is an external file does *not* die by itself. So, emake, do*, etc..
> 
> %% grep -c die * |grep -v ":0"
> ebuild.sh:61
> etc-update:14
> isolated-functions.sh:18
> misc-functions.sh:26
> repoman:2
> 
> I believe this is because you can have those functions in a subshell and
> then die won't behave predictably. I'm sure some PM people will correct
> me if I am wrong. ;)
> 
> -Jeremy
> 
> 

From my knowledge and experience with sunrise:

some functions that dont need "|| die":
epatch, econf, eqmake3, eqmake4

some functions that need "|| die":
emake, do*

Afaik die wont work in a subshell independent of how it is called, so the die from econf wont work,
but also the "emake || die" one would also not work.

-- 
Thomas Sachau

Gentoo Linux Developer


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