From 1a0b941b2c80fa569b31a578cbd933b6c0031d09 Mon Sep 17 00:00:00 2001
From: Zac Medico <zmedico@gentoo.org>
Date: Wed, 9 Apr 2008 05:29:31 +0000
Subject: Handle issues with newlines in elog messages that can trigger an
 unhandled ValueError to be raised from a split() call inside
 collect_ebuild_messages(): * Use \0 to delimit messages, so that that elog
 messages containing newlines   are handled correctly. * Handle a potential
 ValueError when splitting the message type.

svn path=/main/trunk/; revision=9763
---
 bin/isolated-functions.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'bin')

diff --git a/bin/isolated-functions.sh b/bin/isolated-functions.sh
index 737c5dfb4..6bd33cb29 100755
--- a/bin/isolated-functions.sh
+++ b/bin/isolated-functions.sh
@@ -170,7 +170,7 @@ elog_base() {
 			return 1
 			;;
 	esac
-	echo -e "${messagetype} $*" >> "${T}/logging/${EBUILD_PHASE:-other}"
+	echo -ne "${messagetype} $*\n\0" >> "${T}/logging/${EBUILD_PHASE:-other}"
 	return 0
 }
 
-- 
cgit v1.2.3-1-g7c22