Excerpts from Junio C Hamano's message of Wed Nov 04 14:56:57 -0500 2009: > What puzzled me was not "why is it not an error but just a warning?", which > is what you just explained, but "why should we even care what value is > being given to begin with?". I'm sorry. I misunderstood then. I think that in most cases, setting either 'yes' or 'no' is wrong, but I wanted to leave the door open for it for the 1%. I thought that a warning message might be noticed and cause someone to rethink. > I am guessing from this description of 'oddball variables' that your > answer to my question is yes. That is, configure.ac writers are > strongly discouraged from using this new macro for variables that > would usually get YesPlease/NoThanks kind of values. Yes, that's correct. This new macro is for variables that are not a simple toggle. It is also distinct from the mechanism used to specify a path for perl, tcl/tk, etc, in that for those, we do want to error out on no. Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting.
Attachment:
signature.asc
Description: PGP signature