lix -

Age	Commit message (Collapse)	Author
2018-05-30	Modularize config settings	Eelco Dolstra
	Allow global config settings to be defined in multiple Config classes. For example, this means that libutil can have settings and evaluator settings can be moved out of libstore. The Config classes are registered in a new GlobalConfig class to which config files etc. are applied. Relevant to https://github.com/NixOS/nix/issues/2009 in that it removes the need for ad hoc handling of useCaseHack, which was the underlying cause of that issue.
2018-02-19	Config::handleUnknownSettings(): Remove unused 'fatal' argument	Eelco Dolstra

2018-02-13	Allow plugins to define new settings.	Shea Levy

2018-02-13	Allow includes from nix.conf	Shea Levy

2017-11-21	Propagate flags like --sandbox to the daemon properly	Eelco Dolstra

2017-10-24	nix: Respect -I, --arg, --argstr	Eelco Dolstra
	Also, random cleanup to argument handling.
2017-07-30	Replace Unicode quotes in user-facing strings by ASCII	Jörg Thalheim
	Relevant RFC: NixOS/rfcs#4 $ ag -l \| xargs sed -i -e "/\"/s/’/'/g;/\"/s/‘/'/g"
2017-06-07	Don't show flags from config settings in "nix --help"	Eelco Dolstra

2017-06-07	nix: Make all options available as flags	Eelco Dolstra
	Thus, instead of ‘--option <name> <value>’, you can write ‘--<name> <value>’. So --option http-connections 100 becomes --http-connections 100 Apart from brevity, the difference is that it's not an error to set a non-existent option via --option, but unrecognized arguments are fatal. Boolean options have special treatment: they're mapped to the argument-less flags ‘--<name>’ and ‘--no-<name>’. E.g. --option auto-optimise-store false becomes --no-auto-optimise-store
2017-05-03	Fix build on gcc 4.9	Eelco Dolstra
	http://hydra.nixos.org/build/52408843
2017-04-28	Hopefully fix the Darwin build	Eelco Dolstra
	http://hydra.nixos.org/build/52080911
2017-04-20	Improve nix show-config --json	Eelco Dolstra
	In particular, show descriptions. This could be used for manpage generation etc.
2017-04-20	Setting: Remove "Tag" template argument	Eelco Dolstra

2017-04-20	Read per-user settings from ~/.config/nix/nix.conf	Eelco Dolstra

2017-04-14	Fix 32-bit build	Eelco Dolstra
	http://hydra.nixos.org/build/51569816
2017-04-13	Convert Settings to the new config system	Eelco Dolstra
	This makes all config options self-documenting. Unknown or unparseable config settings and --option flags now cause a warning.
2017-04-13	Support arbitrary numeric types for settings	Eelco Dolstra

2017-04-13	Validate Boolean settings better	Eelco Dolstra

2017-04-13	Add a Config class to simplify adding configuration settings	Eelco Dolstra
	The typical use is to inherit Config and add Setting<T> members: class MyClass : private Config { Setting<int> foo{this, 123, "foo", "the number of foos to use"}; Setting<std::string> bar{this, "blabla", "bar", "the name of the bar"}; MyClass() : Config(readConfigFile("/etc/my-app.conf")) { std::cout << foo << "\n"; // will print 123 unless overriden } }; Currently, this is used by Store and its subclasses for store parameters. You now get a warning if you specify a non-existant store parameter in a store URI.