ports/64037 and the alleged && -> ; failure from March 2002
ma at dt.e-technik.uni-dortmund.de
Fri Apr 2 01:51:40 PST 2004
Oliver Eikemeier <eikemeier at fillmore-labs.com> writes:
>> Seriously, whether we use gmake or make for ports does not matter,
>> neither documents the "make passes -e to /bin/sh" behaviour, hence it
>> must not be relied on under any circumstances.
> Use the source, Luke ;) Submit a patch to the manpage.
Wrong approach. Why cast make internals in concrete?
The point is that I do not condone && being changed back to ; on the
assumption that make uses -e, or ";" -> "&&" being rejected.
I don't care how somebody else makes a non-robust port.
Encrypt your mail: my GnuPG key ID is 0x052E7D95
More information about the freebsd-ports