Follow-up Comment #8, bug #66085 (group groff): [comment #7 comment #7:] > why _shouldn't_ a build use $PATH to resolve command names?
Because essential system commands live in predictable places and are the most
likely to do what's intended. An aberrant path might not even include /bin at
all, but a robust Makefile need not care.
Now, is that reason enough to bypass the well-established PATH mechanism for
finding executables, and reinvent this part of the wheel within a Makefile?
Clearly not, according to people who write a ton more Makefiles than I do.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?66085>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
