--enable-feature and configuration failures

[Tim Müller]

On Wed, 2016-06-22 at 14:28 +0200, Xabier Rodríguez Calvar wrote:

Hi,

> IMHO, a better behavior would be:
> 
> --disable-feature: it disables the feature even if the dependencies
> are
> present (quite logical)
> nothing: if the default is true, it checks for the dependencies and
> if
> they are present the module is built (logical too)
> --enable-feature: the user has explicitly requested to build this
> module, if the dependencies are present, everybody is happy. If the
> dependencies are not present, the configuration should fail and
> report that some dependencies are missing, cause the user explicitle
> requested that module.
> 
> Wdyt?

Sounds fine, just needs someone to implement it. There might be a bug
about it already (don't think there was a patch, but didn't check).

Cheers
 -Tim

-- 

Tim Müller, Centricular Ltd - http://www.centricular.com