So now that DEFAULT_SRC_CONFIGURE_TESTS has been added to paludis scm allowing expecting_tests() to take two additional arguments the idea to do the same thing to option() have come up.
Originally optionq() was supposed to be quiet and optionv() was supposed to be verbose. So far option() has just been an alias for optionq(). Instead it is suggested that optionq() and optionv() can remain unchanged while option() will optionally accept two additional arguments. Thus `option foo --foo=yes --foo=no` will print --foo=yes if foo is enabled and --foo=no if foo is disabled. The return value will remain unchanged. This also allows us to add a new DEFAULT_SRC_CONFIGURE_OPTIONS parameter that can be set in global scope to pass simple strings that don't quite match the standard behaviour of option_enable or option_with to econf() if an option is enabled or disabled. _______________________________________________ Exherbo-dev mailing list [email protected] http://lists.exherbo.org/mailman/listinfo/exherbo-dev
