![]() 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
|
||
---|---|---|
.. | ||
.gitignore | ||
cat-test-file | ||
edit-script.sh.in | ||
meson-make-symlink.sh | ||
print-failed-test-output | ||
script-wrapper.sh.in | ||
update-copyright | ||
update-po |