Re: [gentoo-dev] would like this settled :)

[Aron Griffis]

Robin H. Johnson wrote:	[Sat Apr 24 2004, 01:47:18PM EDT]
> As simple as this sounds, it doesn't work, because the die call inside
> econf never lets us reach this code.

You can do put it in a subshell

    if ! ( econf ); then

But this really sucks.  die is designed to tell you at what line, with
a custom message, an ebuild failed.  When functions in ebuild.sh call
die directly, then both those features are thwarted.  The line number
is useless (we don't _care_ where it died in ebuild.sh) and the
message is hard-coded.

Consider an ebuild with the following:

    cd dir1;    econf
    cd ../dir2; econf
    cd ../dir3; econf

In this case the message will currently be the same regardless of
which ebuild fails!  How annoying.  Could we please fix this in
ebuild.sh so that exceptions are propagated to the caller as return
status, which can then call die on its own?

    cd dir1;    econf || die "econf failed in dir1"
    cd ../dir2; econf || die "econf failed in dir2"
    cd ../dir3; econf || die "econf failed in dir3"

Regards,
Aron

--
Aron Griffis
Gentoo Linux Developer (alpha / baselayout / ia64 / mozilla / mutt / ruby / vim)