On Sun, Jun 8, 2008 at 8:57 PM, Ciaran McCreesh
<ciaran.mccreesh@...> wrote:
[...]
>> I didn't understand you. Even if the external binary can't call die,
>> what's to prevent the caller from dying based on the return value of
>> the called binary?
>
> Then we're back to having people do dobin || die, which is precisely
> what we're trying to solve.

Not really. Can't dobin be like so:

fail() {
    if hasq strict FEATURES; then
        die "$@"
    else
        ewarn "QA Notice: ${@}. blah foo"
}

dobin() {
    dobin.sh "${@}" || fail "dobin failed"
}

>> It should not be necessary to define a new EAPI to make sure packages
>> are not broken.
>
> Yes it should. It's a change in behaviour in functionality upon which
> quite a lot of things depend.

This is not functionality. It is the lack thereof. Making this part of
an EAPI makes it opt-in, which it shouldn't be. It is important for QA
and should be mandatory for all ebuilds.

Regards,
-- 
Arun Raghavan
(http://nemesis.accosted.net)
v2sw5Chw4+5ln4pr6$OFck2ma4+9u8w3+1!m?l7+9GSCKi056
e6+9i4b8/9HTAen4+5g4/8APa2Xs8r1/2p5-8 hackerkey.com
-- 
gentoo-dev@g.o mailing list