From 9bf3d6a7603bf48771a20d1f4bd789670e7446f7 Mon Sep 17 00:00:00 2001 From: Eli Schwartz Date: Sat, 13 Mar 2021 22:06:00 -0500 Subject: remove sed command lookup and hardcoding in edit-script.sh We should not need to hardcode the path to sed as we simply don't care. We don't check what kind of sed we found, and we're using the same one we initially found on the PATH, which is surely still on the PATH. At one point we did care to find the system copy of sed and hardcode it in makepkg, because we also passed non-portable -i options to it and makepkg needed to continue working on macOS even if some incompatible GNU sed got installed afterward, elsewhere on the PATH. But this was never relevant to the in-tree buildsystem script running sed. In commit 3a814ee6bca9ee24a868c0dc032b321048a53e08 we removed even that, so we don't need to look it up at all. Signed-off-by: Eli Schwartz Signed-off-by: Allan McRae --- build-aux/edit-script.sh.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'build-aux') diff --git a/build-aux/edit-script.sh.in b/build-aux/edit-script.sh.in index 661c22d5..85c56cfe 100644 --- a/build-aux/edit-script.sh.in +++ b/build-aux/edit-script.sh.in @@ -4,7 +4,7 @@ input=$1 output=$2 mode=$3 -"@SED@" \ +sed \ -e "s|@rootdir[@]|@ROOTDIR@|g" \ -e "s|@localedir[@]|@LOCALEDIR@|g" \ -e "s|@sysconfdir[@]|@sysconfdir@|g" \ -- cgit v1.2.3-70-g09d2