7 commits

Author	SHA1	Message	Date
Eelco Dolstra	4410e9d995	Setting: Remove "Tag" template argument	2017-04-20 16:52:53 +02:00
Eelco Dolstra	f05d5f89ff	Read per-user settings from ~/.config/nix/nix.conf	2017-04-20 14:58:16 +02:00
Eelco Dolstra	6520b757c5	Fix 32-bit build ... http://hydra.nixos.org/build/51569816	2017-04-14 13:59:39 +02:00
Eelco Dolstra	ba9ad29fdb	Convert Settings to the new config system ... This makes all config options self-documenting. Unknown or unparseable config settings and --option flags now cause a warning.	2017-04-13 20:53:23 +02:00
Eelco Dolstra	6bd9576aeb	Support arbitrary numeric types for settings	2017-04-13 17:54:05 +02:00
Eelco Dolstra	0bf34de43b	Validate Boolean settings better	2017-04-13 16:31:28 +02:00
Eelco Dolstra	2040240e23	Add a Config class to simplify adding configuration settings ... 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.	2017-04-13 16:03:31 +02:00