···11+From 81cf57e4653360af7f1718391e424fa05d8ea000 Mon Sep 17 00:00:00 2001
22+From: Keshav Kini <keshav.kini@gmail.com>
33+Date: Thu, 9 Aug 2018 18:36:15 -0700
44+Subject: [PATCH] Use `rm` from PATH
55+66+On NixOS (a Linux distribution), there is no `/bin/rm`, but an `rm`
77+command will generally be available in one's path when running shell
88+scripts. Here, I change a couple of invocations of `/bin/rm` into
99+invocations of `rm` to deal with this issue.
1010+1111+Since `rm` is already called elsewhere in the script without an
1212+absolute path, I assume this change will not cause any
1313+regressions. Still, I've tested this on a CentOS machine and a NixOS
1414+machine, though not other platforms.
1515+---
1616+ makeself-header.sh | 4 ++--
1717+ 1 file changed, 2 insertions(+), 2 deletions(-)
1818+1919+diff --git a/makeself-header.sh b/makeself-header.sh
2020+index 4d2c005..2babf34 100755
2121+--- a/makeself-header.sh
2222++++ b/makeself-header.sh
2323+@@ -515,7 +515,7 @@ if test x"\$quiet" = xn; then
2424+ fi
2525+ res=3
2626+ if test x"\$keep" = xn; then
2727+- trap 'echo Signal caught, cleaning up >&2; cd \$TMPROOT; /bin/rm -rf "\$tmpdir"; eval \$finish; exit 15' 1 2 3 15
2828++ trap 'echo Signal caught, cleaning up >&2; cd \$TMPROOT; rm -rf "\$tmpdir"; eval \$finish; exit 15' 1 2 3 15
2929+ fi
3030+3131+ if test x"\$nodiskspace" = xn; then
3232+@@ -581,7 +581,7 @@ if test x"\$script" != x; then
3333+ fi
3434+ if test x"\$keep" = xn; then
3535+ cd "\$TMPROOT"
3636+- /bin/rm -rf "\$tmpdir"
3737++ rm -rf "\$tmpdir"
3838+ fi
3939+ eval \$finish; exit \$res
4040+ EOF
4141+--
4242+2.14.1
4343+