projects / portage.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 46abb3e) | patch
Use _doebuild_exit_status_check() for unsuccessful return codes (no just
authorZac Medico <zmedico@gentoo.org>
Fri, 10 Apr 2009 01:02:29 +0000 (01:02 -0000)
committerZac Medico <zmedico@gentoo.org>
Fri, 10 Apr 2009 01:02:29 +0000 (01:02 -0000)
commit3d819dc230439c4bde66d6689744fee6205fb291
tree7523236ec18e0aee97e0352337f9212d9a96ab70tree | snapshot
parent46abb3e7b0386422960e01e5adc27f2a25fc2973commit | diff
Use _doebuild_exit_status_check() for unsuccessful return codes (no just
successful ones), since we want to be sure to produce an informative warning
message whenever the shell exits unexpectedly (whether it's successful or
unsuccessful). This is important since it can be makes these kinds of issues
easier to diagnose (otherwise the user might blame portage, when it's really
the ebuild/eclasses that is at fault).

svn path=/main/trunk/; revision=13311
pym/portage/__init__.py diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.