fork/home-manager
git clone https://git.julia.blue/fork/home-manager
33ccc5c2
master
1[[sec-release-22.11]] 2== Release 22.11 3 4The 22.11 release branch became the stable branch in November, 2022. 5 6[[sec-release-22.11-highlights]] 7=== Highlights 8 9This release has the following notable changes: 10 11* The <<opt-home.stateVersion>> option no longer has a default value. 12It used to default to ``18.09'', which was the Home Manager version 13that introduced the option. If your configuration does not explicitly 14set this option then you need to add 15+ 16[ source,nix ] 17home.stateVersion = "18.09"; 18+ 19to your configuration. 20 21* The Flake function `homeManagerConfiguration` has been simplified. 22Specifically, the arguments 23+ 24-- 25- `configuration`, 26- `username`, 27- `homeDirectory`, 28- `stateVersion`, 29- `extraModules`, and 30- `system` 31-- 32+ 33have been removed. Instead use the new `modules` argument, which 34accepts a list of NixOS modules. 35+ 36Further, the `pkgs` argument is now mandatory and should be set to 37`nixpkgs.legacyPackages.${system}` where `nixpkgs` is the Nixpkgs 38input of your choice. 39+ 40For example, if your Flake currently contains 41+ 42[ source,nix ] 43---- 44homeManagerConfiguration { 45configuration = import ./home.nix; 46system = "x86_64-linux"; 47username = "jdoe"; 48homeDirectory = "/home/jdoe"; 49stateVersion = "22.05"; 50extraModules = [ ./some-extra-module.nix ]; 51} 52---- 53+ 54then you can change it to 55+ 56[ source,nix ] 57---- 58homeManagerConfiguration { 59pkgs = nixpkgs.legacyPackages.${system}; 60modules = [ 61./home.nix 62./some-extra-module.nix 63{ 64home = { 65username = "jdoe"; 66homeDirectory = "/home/jdoe"; 67stateVersion = "22.05"; 68}; 69} 70]; 71} 72---- 73+ 74Of course, you can move the assignment of <<opt-home.username>>, 75<<opt-home.homeDirectory>>, and <<opt-home.stateVersion>> to some 76other file or simply place them in your `home.nix`. 77 78* The `services.picom` module has been refactored to use structural 79settings. 80+ 81As a result `services.picom.extraOptions` has been removed in favor of 82<<opt-services.picom.settings>>. Also, `services.picom.blur*` were 83removed since upstream changed the blur settings to be more flexible. 84You can migrate the blur settings to use 85<<opt-services.picom.settings>> instead. 86 87* The `services.compton` module has been removed. It was deprecated in 88release 20.03. Use `services.picom` instead. 89 90[[sec-release-22.11-state-version-changes]] 91=== State Version Changes 92 93The state version in this release includes the changes below. 94These changes are only active if the `home.stateVersion` option is set to "22.11" or later. 95 96* The <<opt-services.mpd.musicDirectory>> option now defaults to the 97value of <<opt-xdg.userDirs.music>> if <<opt-xdg.userDirs.enable>> is 98enabled. Otherwise it is undefined and must be specified in the user 99configuration. 100 101* The activation script now resets `PATH` before running. Before, the 102user's `PATH` environment variable would be used in the script and 103this made it possible for commands in the activation script to run 104arbitrary commands accessible to the user. We now restrict the 105activation script to commands that are explicitly specified. 106+ 107There is no official way to restore the old behavior. We attempt to 108make the activation script as reproducible as possible and honoring 109the user's `PATH` reduces reproducibility. 110+ 111If you need to run a command in an activation script block then refer 112to the command by its absolute command path, such as 113`${pkgs.hello}/bin/hello`.