lix -

Age	Commit message (Collapse)	Author
2023-06-18	Split `OptionalPathSetting` from `PathSetting`	John Ericson
	Rather than doing `allowEmpty` as boolean, have separate types and use `std::optional`. This makes it harder to forget the possibility of an empty path. The `build-hook` setting was categorized as a `PathSetting`, but actually it was split into arguments. No good! Now, it is `Setting<Strings>` which actually reflects what it means and how it is used. Because of the subtyping, we now also have support for `Setting<std::optional<String>>` in general. I imagine this can be used to clean up many more settings also.
2023-04-17	Fix some issues with experimental config settings	John Ericson
	Issues: 1. Features gated on disabled experimental settings should warn and be ignored, not silently succeed. 2. Experimental settings in the same config "batch" (file or env var) as the enabling of the experimental feature should work. 3. For (2), the order should not matter. These are analogous to the issues @roberth caught with my changes for arg handling, but they are instead for config handling. Co-authored-by: Robert Hensing <roberth@users.noreply.github.com>
2023-04-16	Mark experimental configuration settings programmatically	John Ericson
	Fix #8162 The test is changed to compare `nlohmann::json` values, not strings of dumped JSON, which allows us to format things more nicely.
2023-04-11	Do not gate or hide experimental settings	John Ericson
	This is somewhat hacky fix just for 2.15. I unintentionally hid them from the manual, when no one wanted to hide them that (including myself). I also required the experimental feature to be enabled in an order-dependent way, which is not good. The simplest fix for this immanent release is just to always show them, and always allow them to be set. Effectively undoes some changes from aa663b7e89d3d02248d37ee9f68b52770b247018
2023-03-20	Fix handling of experimental features mid-parse	John Ericson
	If we conditionally "declare" the argument, as we did before, based upon weather the feature is enabled, commands like nix --experimental-features=foo ... --thing-gated-on-foo won't work, because the experimental feature isn't enabled until after we start parsing. Instead, allow arguments to also be associated with experimental features (just as we did for builtins and settings), and then the command line parser will filter out the experimental ones. Since the effects of arguments (handler functions) are performed right away, we get the required behavior: earlier arguments can enable later arguments enabled! There is just one catch: we want to keep non-positional flags...non-positional. So if nix --experimental-features=foo ... --thing-gated-on-foo works, then nix --thing-gated-on-foo --experimental-features=foo ... should also work. This is not my favorite long-term solution, but for now this is implemented by delaying the requirement of needed experimental features until after all the arguments have been parsed.
2023-03-20	Mark experimental features on settings	John Ericson
	We hide them in various ways if the experimental feature isn't enabled. To do this, we had to move the experimental features list out of libnixstore, because the setting machinary itself depends on it. To do that, we made a new `ExperimentalFeatureSettings`.
2023-03-20	Move enabled experimental feature to libutil struct	John Ericson
	This is needed in subsequent commits to allow the settings and CLI args infrastructure itself to read this setting.
2022-10-22	Fix C++20 warnings	Graham Bennett

2022-02-25	Remove std::string alias (for real this time)	Eelco Dolstra
	Also use std::string_view in a few more places.
2022-02-21	Remove std::vector alias	Eelco Dolstra

2021-10-27	Style	Eelco Dolstra

2021-10-26	Make experimental-features a proper type	regnat
	Rather than having them plain strings scattered through the whole codebase, create an enum containing all the known experimental features. This means that - Nix can now `warn` when an unkwown experimental feature is passed (making it much nicer to spot typos and spot deprecated features) - It’s now easy to remove a feature altogether (once the feature isn’t experimental anymore or is dropped) by just removing the field for the enum and letting the compiler point us to all the now invalid usages of it.
2021-09-22	Make setDefault() typed	Eelco Dolstra

2021-07-15	Forward the whole Nix config to the post-build-hook	regnat
	Fill `NIX_CONFIG` with the value of the current Nix configuration before calling the post-build-hook. That way the whole configuration (including the possible `experimental-features`, a possibly `--store` option or whatever) will be made available to the hook
2021-03-26	Fix some typos	Eelco Dolstra
	Fixes #4671.
2021-01-08	string2Int(): Return std::optional	Eelco Dolstra

2020-11-09	Fix appending to Setting<StringSet>	Eelco Dolstra
	Fixes: warning: unknown setting 'extra-sandbox-paths'
2020-10-29	Fix assertion failure in tab completion for --option	Eelco Dolstra

2020-10-29	Generalize extra-* settings	Eelco Dolstra
	This removes the extra-substituters and extra-sandbox-paths settings and instead makes every array setting extensible by setting "extra-<name> = <value>" in the configuration file or passing "--<name> <value>" on the command line.
2020-10-26	BaseSetting<StringMap>::set(): Don't append to previous value	Eelco Dolstra

2020-09-29	Merge branch 'master' into access-tokens	Kevin Quick

2020-09-24	Support StringMap configuration settings.	Kevin Quick
	Allows Configuration values that are space-separated key=value pairs.
2020-09-21	abstractsettingtojson.hh -> abstract-setting-to-json.hh	Eelco Dolstra

2020-09-16	Don't include nlohmann/json.hpp in config.hh	regnat
	Instead make a separate header with the template implementation of `BaseSetting<T>::toJSONObj` that can be included where needed
2020-09-16	Complete the `toJSON` instance for `Setting<T>`	regnat
	Don't let it just contain the value, but also the other fields of the setting (description, aliases, etc..)
2020-08-20	Allow 'nix' subcommands to provide docs in Markdown format	Eelco Dolstra

2020-08-20	List deprecated option aliases in the docs	Eelco Dolstra

2020-08-20	Config: Use nlohmann/json	Eelco Dolstra

2020-08-19	Generate the nix.conf docs from the source code	Eelco Dolstra
	This means we don't have two (divergent) sets of option descriptions anymore.
2020-05-27	config.cc: extract parts of applyConfigFile into applyConfig	Andreas Rammhold
	This moves the actual parsing of configuration contents into applyConfig which applyConfigFile is then going to call. By changing this we can now test the configuration file parsing without actually create a file on disk.
2020-05-04	Flag: Use designated initializers	Eelco Dolstra

2019-12-17	Add priority setting to stores	Eelco Dolstra
	This allows overriding the priority of substituters, e.g. $ nix-store --store ~/my-nix/ -r /nix/store/df3m4da96d84ljzxx4mygfshm1p0r2n3-geeqie-1.4 \ --substituters 'http://cache.nixos.org?priority=100 daemon?priority=10' Fixes #3264.
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