projects / portage.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 4695b5f) | patch
Use _doebuild_exit_status_check() for unsuccessful return codes (no just
authorZac Medico <zmedico@gentoo.org>
Thu, 30 Apr 2009 07:03:30 +0000 (07:03 -0000)
committerZac Medico <zmedico@gentoo.org>
Thu, 30 Apr 2009 07:03:30 +0000 (07:03 -0000)
commit848f0dc89a8c5ff035574439a9894e54bc37200e
treeb92af43bc8df5580dfa1d7ce0e3b1b14bf6523d1tree | snapshot
parent4695b5fc8d7c9b5e9323cf1d166f9f647b92d541commit | 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). (trunk r13311)

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