true/false vs. yes/no

[Erik Joelsson]

I think this is something that we need to clean up or at least define 
clearly when what is used. I would guess that the variable in make 
inherited its values from the old build and that in configure we used 
the configure standard.

/Erik

On 2012-10-05 09:27, Mario Torre wrote:
> Don't know about the variable value (does seem a bit inconsistent indeed,
> although it makes some sense) but the yes/no is AFAIK pretty standard.
>
> For example, this comes from the GNU.org guides (
> http://www.gnu.org/prep/standards/html_node/Configuration.html):
>
> """
> Configure the package to build and install an optional user-level
> facility called feature.  This allows users to choose which
> optional features to include.  Giving an optional parameter of
> ‘no’ should omit feature, if it is built by default.
> """
>
> I guess the variable value makes some sense, since false is the value
> assigned by answering "no" to the enable question.
>
> Mario
>
> Il giorno giovedì 4 ottobre 2012, David Holmes<david.holmes at oracle.com>  ha
> scritto:
>> Just got bitten by the fact that the --enable-jfr flag takes the values
> yes or no when passed to configure, but the ENABLE_JFR variable gets set to
> true or false.
>> Is there a reason for this inconsistency (is it normal for configure
> based systems)?
>> David
>>