From: Zac Medico <zmedico@gentoo.org>
Date: Tue, 1 Feb 2011 09:54:01 +0000 (-0800)
Subject: doebuild: always return success for listonly mode
X-Git-Tag: v2.2.0_alpha20~40
X-Git-Url: http://git.tremily.us/gitweb.cgi?a=commitdiff_plain;h=6343797bc73159dd8b140b378a90b23fcb841d4c;p=portage.git

doebuild: always return success for listonly mode

This compensates for changed fetch() return value in commit
394cd4a00d37fd078f8dd40f89f8c810355d7816, which serves to
trigger the pkg_nofetch phase inside doebuild().
---

diff --git a/pym/portage/package/ebuild/doebuild.py b/pym/portage/package/ebuild/doebuild.py
index 6fc7489aa..bbc3a4a12 100644
--- a/pym/portage/package/ebuild/doebuild.py
+++ b/pym/portage/package/ebuild/doebuild.py
@@ -737,6 +737,12 @@ def doebuild(myebuild, mydo, myroot, mysettings, debug=0, listonly=0,
 			if not fetch(fetchme, mysettings, listonly=listonly,
 				fetchonly=fetchonly):
 				spawn_nofetch(mydbapi, myebuild, settings=mysettings)
+				if listonly:
+					# The convention for listonly mode is to report
+					# success in any case, even though fetch() may
+					# return unsuccessfully in order to trigger the
+					# nofetch phase.
+					return 0
 				return 1
 
 		if mydo == "fetch":