Prior to commit a141d715
, CMD_NOINSTALL had no default set, but most of the usages were of the form "! isTrue ${CMD_NOINSTALL}", which on an unset value, came out as false. These were replaced by "isTrue ${CMD_INSTALL}", but my analysis of the needed default value was wrong, and was set to false instead of true.
Signed-off-by: Robin H. Johnson <robbat2@orbis-terrarum.net>cleanup-cruft
parent
146934e1a8
commit
b49f1f377d
Loading…
Reference in new issue