Danylo Hlynskyi 60e8fcf0e5 module system: revert "remove types.optionSet", just deprecate (#56857) ... The explicit remove helped to uncover some hidden uses of `optionSet` in NixOps. However it makes life harder for end-users of NixOps - it will be impossible to deploy 19.03 systems with old NixOps, but there is no new release of NixOps with `optionSet` fixes. Also, "deprecation" process isn't well defined. Even that `optionSet` was declared "deprecated" for many years, it was never announced. Hence, I leave "deprecation" announce. Then, 3 releases after announce, we can announce removal of this feature. This type has to be removed, not `throw`-ed in runtime, because it makes some perfectly fine code to fail. For example: ``` $ nix-instantiate --eval -E '(import <nixpkgs/lib>).types' --strict trace: `types.list` is deprecated; use `types.listOf` instead error: types.optionSet is deprecated; use types.submodule instead (use '--show-trace' to show detailed location information) ```		2019-03-07 21:28:09 +02:00
..
manual	module system: revert "remove types.optionSet", just deprecate (#56857)	2019-03-07 21:28:09 +02:00
varlistentry-fixer.rb	doc: Adds xml fixing script. (see previous and next commits)	2018-05-31 21:02:15 -04:00
xmlformat.conf	doc: Adds rule to xmlformat to help keep spacing right.	2018-05-31 21:02:15 -04:00