From 400a1fc781b11dc00c47880138f43052b006c3da Mon Sep 17 00:00:00 2001
From: Jim Meyering <jim@meyering.net>
Date: Sun, 8 Feb 2004 10:00:38 +0000
Subject: Avoid triggering a bug in OSF/Tru64's sed that would cause an
 unwarranted test failure.

---
 tests/rm/rm5 | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)

(limited to 'tests/rm/rm5')

diff --git a/tests/rm/rm5 b/tests/rm/rm5
index 91715ae75..a1f3231af 100755
--- a/tests/rm/rm5
+++ b/tests/rm/rm5
@@ -39,9 +39,13 @@ fi
 fail=0
 
 rm -ir d < in > out 2>&1 || fail=1
-# The following loses with Tru64's sed, since that sed mistakenly
-# tacks a newline onto the end of the file.
-tr '?' '\n' < out |sed 's/^ //' > o2
+
+# Given input like `rm: ...? rm: ...? ' (no trailing newline),
+# the `head...' part of the pipeline below removes the trailing space, so
+# that sed doesn't have to deal with a line lacking a terminating newline.
+# This avoids a bug whereby some vendor-provided (Tru64) versions of sed
+# would mistakenly tack a newline onto the end of the output.
+tr '?' '\n' < out | head --bytes=-1 | sed 's/^ //' > o2
 mv o2 out
 
 # Make sure it's been removed.
-- 
cgit v1.2.3-54-g00ecf