Modules compilation should be configurable with yes/no/auto option

[GoogleCodeExporter]

Currently modules are compile automatically if dependencies are satisfied. 
To be packager friendly it would be better if every modules provides an 
option with value yes/no/auto (auto being default) so we can explicitly 
enable (in with case configuration will fail if deps is missing), disable or 
let the configurator decide.

Original issue reported on code.google.com by nicolas.dufresne@gmail.com on 29 Mar 2010 at 4:20

[GoogleCodeExporter]

I think that this just adds complication without any real benefit.  The only 
platform 
where this should matter is Linux and on Linux there are two cases of someone 
building libproxy: packagers and end-users.

Packagers should enable all options.  End-users should set all deps to auto.  
Thus, 
the "no" option is never needed.  Upon further inspection, the packager also 
has to 
specify appropriate deps.  So the "yes" option is never needed.  This leaves us 
with 
"auto" which is what we currently do.

However, if you can give me a specific use case, I'm willing to rethink this 
approach.

Original comment by npmccallum@gmail.com on 29 Mar 2010 at 5:15

• Changed state: WontFix