For example, if inherit eutils is missing, the following error will be shown: /var/tmp/portage/***/***/temp/environment: line 701: epatch: command not found But emerge will continue merging package that will result in, sometimes, a buggy app. I think that emerge should die like currently does when, for example, cannot apply a wrong patch Thanks a lot Reproducible: Always
*** This bug has been marked as a duplicate of bug 138792 ***
Well, unless the other bug is meant to make _everything_ die by default on failure and not just the known wrappers mentioned there, this is not a dupe really. This one is meant to catch typos, missing inherits etc. resulting in "command not found" stuff.
(In reply to comment #2) > This one is meant to catch typos, missing inherits etc. resulting in > "command not found" stuff. > +1
Oh, I see what you want, but it doesn't seem possible to fix. Ideas?
(In reply to comment #4) > Oh, I see what you want, but it doesn't seem possible to fix. Ideas? Well, unfortunately not ATM (beyond nasty stuff like grep emerge.log after each phase :P) but it'd be nice thing to have. *g*
(In reply to comment #4) > Oh, I see what you want, but it doesn't seem possible to fix. Ideas? > I don't know much about these things :'( , but I have seen that adding a "die" to epatch line: epatch ..... || die Does the trick, Isn't there any way for do this by default, for not needing to add "die" to all ebuilds that use epatch? Thanks a lot ___ Should I reopen this bug?
Created attachment 144304 [details] trap ERR (In reply to comment #6) > I don't know much about these things :'( , but I have seen that adding a "die" > to epatch line: > epatch ..... || die That works but it's something that has to be done in the ebuild or eclass, not in portage. Also, note that the intention of bug 138792 is to eliminate the need for adding "|| die" in places like this. Alternatively, we could use a trap to call die, as demonstrated in the attached script. This approach would be quite similar in effect to bug 138792 and would also require an EAPI bump since it would be incompatible with a majority of the current ebuilds and eclasses. I imagine that people who support the inclusion of bug 138792 would also be likely to support the trap approach since it is so similar.
OK, thanks for info