<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 4 March 2015 at 21:49, D. Hugh Redelmeier <span dir="ltr"><<a href="mailto:hugh@mimosa.com" target="_blank">hugh@mimosa.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">| From: Paul Wouters <<a href="mailto:paul@nohats.ca">paul@nohats.ca</a>><br>
<span class=""><br>
| you often need to add FORCE=1 (I know you love these tweaks :)<br>
<br>
</span>I've not looked at any of the details, so this is just principle:<br>
the polite way of telling make to do something is a target, not adding<br>
definitions.<br>
<br>
Not totally unrelated: I would like our scripts to work with<br>
--warn-undefined-variables. I know, I'm repeating myself.<br></blockquote><br></div><div class="gmail_quote">I suspect FORCE=tiddles-the-cat will enable the same feature. With makefiles, it is easier to test empty/non-empty than specific values.<br><br></div><div class="gmail_quote">I tweaked my kvm-* targets to print the value of any make variable they use. If nothing else it helps me with debugging.<br></div><div class="gmail_quote"><div> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
FORCE=1 suggests the questions:<br>
What does FORCE=0 mean?<br>
What does FORCE=2 mean?<br>
What does FORCE=no mean?<br>
<div class="HOEnZb"><div class="h5">_______________________________________________<br>
Swan-dev mailing list<br>
<a href="mailto:Swan-dev@lists.libreswan.org">Swan-dev@lists.libreswan.org</a><br>
<a href="https://lists.libreswan.org/mailman/listinfo/swan-dev" target="_blank">https://lists.libreswan.org/mailman/listinfo/swan-dev</a><br>
</div></div></blockquote></div><br></div></div>