fork/home-manager
git clone https://git.julia.blue/fork/home-manager
7ef3db37
master
1[[sec-release-20.03]] 2== Release 20.03 3 4The 20.03 release branch became the stable branch in April, 2020. 5 6[[sec-release-20.03-highlights]] 7=== Highlights 8 9This release has the following notable changes: 10 11* Assigning a list to the <<opt-home.file>>, <<opt-xdg.configFile>>, 12and <<opt-xdg.dataFile>> options is now deprecated and will produce a 13warning message if used. Specifically, if your configuration currently 14contains something like 15+ 16[ source,nix ] 17---- 18home.file = [ 19{ 20target = ".config/foo.txt"; 21text = "bar"; 22} 23] 24---- 25+ 26then it should be updated to instead use the equivalent attribute set form 27+ 28[ source,nix ] 29---- 30home.file = { 31".config/foo.txt".text = "bar"; 32} 33---- 34+ 35Support for the list form will be removed in Home Manager version 3620.09. 37 38* The `lib` function attribute given to modules is now enriched with 39an attribute `hm` containing extra library functions specific for Home 40Manager. More specifically, `lib.hm` is now the same as `config.lib` 41and should be the preferred choice since it is more robust. 42+ 43Therefore, if your configuration makes use of, for example, 44`config.lib.dag` to create activation script blocks, it is recommended 45to change to `lib.hm.dag`. 46+ 47Note, in the unlikely case that you are 48+ 49** using Home Manager's NixOS or nix-darwin module, 50** have made your own Home Manager module containing an top-level 51option named `config` or `options`, and 52** assign to this option in your system configuration inside a plain 53attribute set, i.e., without a function argument, 54 55+ 56then you must update your configuration to perform the option 57assignment inside a `config` attribute. For example, instead of 58+ 59[ source,nix ] 60---- 61home-manager.users.jane = { config = "foo"; }; 62---- 63+ 64use 65+ 66[ source,nix ] 67---- 68home-manager.users.jane = { config.config = "foo"; }; 69---- 70 71* The `services.compton` module has been deprecated and instead the 72new module `services.picom` should be used. This is because Nixpkgs no 73longer packages compton, and instead packages the (mostly) compatible 74fork called picom. 75 76* The list form of the <<opt-programs.ssh.matchBlocks>> option has 77been deprecated and configurations requiring match blocks in a defined 78order should switch to using DAG entries instead. For example, a 79configuration 80+ 81[ source,nix ] 82---- 83programs.ssh.matchBlocks = [ 84{ 85host = "alpha.foo.com"; 86user = "jd"; 87} 88{ 89host = "*.foo.com"; 90user = "john.doe"; 91} 92]; 93---- 94+ 95can be expressed along the lines of 96+ 97[ source,nix ] 98---- 99programs.ssh.matchBlocks = { 100"*.example.com" = { 101user = "john.doe"; 102} 103"alpha.example.com" = lib.hm.dag.entryBefore ["*.example.com"] { 104user = "jd"; 105} 106}; 107---- 108+ 109Support for the list form will be removed in Home Manager version 11020.09. 111 112[[sec-release-20.03-state-version-changes]] 113=== State Version Changes 114 115The state version in this release includes the changes below. These 116changes are only active if the `home.stateVersion` option is set to 117"20.03" or later. 118 119* The <<opt-programs.zsh.history.path>> option is no longer prepended 120by `$HOME`, which allows specifying absolute paths, for example, 121using the xdg module. Also, the default value is fixed to 122`$HOME/.zsh_history` and `dotDir` path is not prepended to it 123anymore. 124* The newsboat module will now default in displaying `queries` before `urls` in 125 its main window. This makes sense in the case when one has a lot of URLs and 126 few queries.