[Exherbo-dev] Additional arguments for option()

Bo Ørsted Andresen zlin at exherbo.org
Wed Oct 17 21:01:26 UTC 2012


On Wed, 19 Sep 2012 11:53:26 +0000
Bo Ørsted Andresen <zlin at exherbo.org> wrote:
> 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.

This was introduced with Paludis 0.80.1.

http://commits.exherbo.org/docs:f0cbba35

If you don't upgrade to it you will start hitting automagic
dependencies as exheres start using it.

-- 
Bo Ørsted Andresen



More information about the Exherbo-dev mailing list