From 191ef888f86d443e8b10505d0d9876eb91dc065f Mon Sep 17 00:00:00 2001 From: Zac Medico Date: Fri, 12 Jan 2007 02:44:24 +0000 Subject: Fix ebuild environment color.map support so that it works properly through exec calls (since the color variables can not be directly exported due to env pollution). svn path=/main/trunk/; revision=5578 --- pym/portage.py | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'pym/portage.py') diff --git a/pym/portage.py b/pym/portage.py index 4bf3a9353..0952bd5f8 100644 --- a/pym/portage.py +++ b/pym/portage.py @@ -2976,8 +2976,10 @@ def doebuild_environment(myebuild, mydo, myroot, mysettings, debug, use_cache, m mysettings["KVERS"]=myso[1] # Allow color.map to control colors associated with einfo, ewarn, etc... + mycolors = [] for c in ("GOOD", "WARN", "BAD", "HILITE", "BRACKET"): - mysettings[c] = output.codes[c] + mycolors.append("%s=$'%s'" % (c, output.codes[c])) + mysettings["PORTAGE_COLORMAP"] = "\n".join(mycolors) def prepare_build_dirs(myroot, mysettings, cleanup): -- cgit v1.2.3-1-g7c22