On Dienstag, 30. September 2008, Thomas Sachau wrote:
>
> 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 c
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 d
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*,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Peter Volkov wrote:
> В Вск, 28/09/2008 в 20:24 +0200, Thomas Sachau пишет:
>> I see many ebuild that still use "econf || die", also econf should die by
>> itself. Are there any
>> specific reasons for this? Some cases where econf does not die also it
Peter Volkov wrote:
> В Вск, 28/09/2008 в 20:24 +0200, Thomas Sachau пишет:
>> I see many ebuild that still use "econf || die", also econf should die by
>> itself.
>
> This || die is redundant. Personally I remove it in every package I
> touch and I suggest others do the same. People use our tre
В Вск, 28/09/2008 в 20:24 +0200, Thomas Sachau пишет:
> I see many ebuild that still use "econf || die", also econf should die by
> itself. Are there any
> specific reasons for this? Some cases where econf does not die also it fails?
> Or some other reason
> for this?
This || die is redundant. P
Thomas Sachau wrote:
> I see many ebuild that still use "econf || die", also econf should die by
> itself. Are there any
> specific reasons for this? Some cases where econf does not die also it fails?
> Or some other reason
> for this?
My guess is that due to the general lack of consistency in w
I see many ebuild that still use "econf || die", also econf should die by
itself. Are there any
specific reasons for this? Some cases where econf does not die also it fails?
Or some other reason
for this?
Some feedback on this would be nice.
Thanks
--
Thomas Sachau
Gentoo Linux Developer
s
