From 537b04902f2082b39bea5d986c443cef7896c1b5 Mon Sep 17 00:00:00 2001 From: rycee Date: Sun, 17 Dec 2023 11:59:49 +0000 Subject: [PATCH] deploy: e4dba0bd01956170667458be7b45f68170a63651 --- index.xhtml | 4 +- release-notes.xhtml | 98 ++++++++++++++++++++++----------------------- 2 files changed, 51 insertions(+), 51 deletions(-) diff --git a/index.xhtml b/index.xhtml index 9709fbbfe..c2236af7a 100644 --- a/index.xhtml +++ b/index.xhtml @@ -29,7 +29,7 @@

Home Manager Manual

-

Version 23.11

+

Version 24.05 (unstable)

@@ -292,7 +292,7 @@ follows:

{ config, pkgs, ... }:
   };
 }

To activate this configuration you can run

home-manager switch
diff --git a/release-notes.xhtml b/release-notes.xhtml
index 39175c727..e3c3de6d1 100644
--- a/release-notes.xhtml
+++ b/release-notes.xhtml
@@ -33,8 +33,8 @@ changes are only active if the home.stateVersion op
 "24.05" or later.
  • Nothing, yet.

 
 
-
 
  
   
    
     Release 23.11   
  
 
 
Table of Contents
 
  
   Highlights 
   State Version Changes 
 
The 23.11 release branch became stable in November, 2023.
 
  
   
    
     Highlights   
  
 
This release has the following notable changes:
 
  
   
    
     Release 23.11   
  
 
 
Table of Contents
 
  
   Highlights 
   State Version Changes 
 
The 23.11 release branch became stable in November, 2023.
 
  
   
    
     Highlights   
  
 
This release has the following notable changes:
 
  
   
    
     Release 22.11   
  
 
 
Table of Contents
 
  
   Highlights 
   State Version Changes 
 
The 22.11 release branch became the stable branch in November, 2022.
 
  
   
    
     Highlights   
  
 
This release has the following notable changes:
 
  
   
    
     Release 22.11   
  
 
 
Table of Contents
 
  
   Highlights 
   State Version Changes 
 
The 22.11 release branch became the stable branch in November, 2022.
 
  
   
    
     Highlights   
  
 
This release has the following notable changes:
  • The home.stateVersion option no longer has a default
 value. It used to default to “18.09”, which was the Home Manager
 version that introduced the option. If your configuration does not
 explicitly set this option then you need to add
    home.stateVersion = "18.09";
@@ -105,20 +105,20 @@ input of your choice.
    For example, if your Flake currently contains
    Of course, you can move the assignment of opt-home.username,
-opt-home.stateVersion to
+

Of course, you can move the assignment of home.username, +home.stateVersion to some other file or simply place them in your home.nix.

  • The services.picom module has been refactored to use structural settings.

    As a result services.picom.extraOptions has been removed in favor -of opt-services.picom.settings. Also, services.picom.blur* +of services.picom.settings. Also, services.picom.blur* were removed since upstream changed the blur settings to be more flexible. You can migrate the blur settings to use -opt-services.picom.settings instead.

  • The services.compton module has been removed. It was deprecated in +services.picom.settings instead.

  • The services.compton module has been removed. It was deprecated in release 20.03. Use services.picom instead.

    • State Version Changes

    The state version in this release includes the changes below. These changes are only active if the home.stateVersion option is set to -"22.11" or later.

    State Version Changes

    The state version in this release includes the changes below. These changes are only active if the home.stateVersion option is set to -"22.05" or later.

    • The opt-programs.waybar.settings option now allows defining -modules directly under opt-programs.waybar.settings. +"22.05" or later.

      • The programs.waybar.settings option now allows defining +modules directly under programs.waybar.settings. Defining modules under programs.waybar.settings.modules will now be an error. For example,

        programs.waybar.settings.modules."custom/my-module" = { };

        becomes

        programs.waybar.settings."custom/my-module" = { };
@@ -169,20 +169,20 @@ has now changed. For associated discussion see
 issue #1906.

      • Rofi version 1.7.0 removed many options that were used by the module and replaced them with custom themes, which are more flexible and powerful.

        You can replicate your old configuration by moving those options to -opt-programs.rofi.theme. Keep in mind that the syntax is +programs.rofi.theme. Keep in mind that the syntax is different so you may need to do some changes.

      • Taskwarrior version 2.6.0 respects XDG Specification for the config -file now. Option opt-programs.taskwarrior.config and friends +file now. Option programs.taskwarrior.config and friends now generate the config file at $XDG_CONFIG_HOME/task/taskrc instead of ~/.taskrc.

    State Version Changes

    The state version in this release includes the changes below. These changes are only active if the home.stateVersion option is set to -"21.11" or later.

    • The opt-home.keyboard option now defaults to null, meaning +"21.11" or later.

      • The home.keyboard option now defaults to null, meaning that Home Manager won’t do any keyboard layout management. For -example, setxkbmap won’t be run in X sessions.

      • The opt-programs.pet.settings option no longer place its +example, setxkbmap won’t be run in X sessions.

      • The programs.pet.settings option no longer place its value inside a General attribute. For example,

        programs.pet.settings.editor = "nvim";

        becomes

        programs.pet.settings.General.editor = "nvim";
-

      • The opt-programs.waybar.settings option now allows defining -modules directly under opt-programs.waybar.settings. For +

      • The programs.waybar.settings option now allows defining +modules directly under programs.waybar.settings. For example,

        programs.waybar.settings.modules."custom/my-module" = { };

        becomes

        programs.waybar.settings."custom/my-module" = { };
      @@ -199,7 +199,7 @@ list items’ invocation keys. For example,

    • The opt-programs.mpv.package option has been changed to
+
    • The programs.mpv.package option has been changed to
 allow custom derivations. The following configuration is now
 possible:
      programs.mpv.package = (pkgs.wrapMpv (pkgs.mpv-unwrapped.override {
   vapoursynthSupport = true;
@@ -208,9 +208,9 @@ possible:
      programs.mpv.package = (pkgs
     "--prefix" "LD_LIBRARY_PATH" ":" "${pkgs.vapoursynth-mvtools}/lib/vapoursynth"
   ];
 });
-
      As a result of this change, opt-programs.mpv.package is no
+
      As a result of this change, programs.mpv.package is no
 longer the resulting derivation. Use the newly introduced
-programs.mpv.finalPackage instead.
    • The opt-programs.rofi.extraConfig option is now an attribute
+programs.mpv.finalPackage instead.
    • The programs.rofi.extraConfig option is now an attribute
 set rather than a string. To migrate, move each line into the
 attribute set, removing the rofi. prefix from the keys. For
 example,
      programs.rofi.extraConfig = ''
@@ -221,7 +221,7 @@ example,
      programs.rofi.extraConfig = &
   show-icons = true;
   modi = "drun,emoji,ssh";
 };
-
    • The opt-programs.rofi.theme option now supports defining a
+
    • The programs.rofi.theme option now supports defining a
 theme using an attribute set, the following configuration is now
 possible:
      programs.rofi.theme = let
   # Necessary to avoid quoting non-string values
@@ -245,7 +245,7 @@ in {
 };
 
    • The services.redshift.extraOptions and
 services.gammastep.extraOptions options were removed in favor of
-opt-services.redshift.settings and
+services.redshift.settings and
 services.gammastep.settings, that are now an attribute set rather
 than a string. They also support new features not available before,
 for example:
      services.redshift = {
@@ -274,10 +274,10 @@ disposal:
      configure.packages.*.opt  -&
 configure.packages.*.start  -> programs.neovim.plugins = [ { plugin = ...; }]
 configure.customRC -> programs.neovim.extraConfig
 
    • Home Manager now respects the NO_COLOR environment variable as per
-https://no-color.org/.
    • Qt module now supports opt-qt.style.name to specify a theme
-name and opt-qt.style.package to specify a theme package. If
-you have set opt-qt.platformTheme to gnome, a
-opt-qt.style.package compatible with both Qt and Gtk is now
+https://no-color.org/.
    • Qt module now supports qt.style.name to specify a theme
+name and qt.style.package to specify a theme package. If
+you have set qt.platformTheme to gnome, a
+qt.style.package compatible with both Qt and Gtk is now
 required to be set. For instance:
      qt = {
   platformTheme = "gnome";
   style = {
@@ -290,9 +290,9 @@ to name. For example:
      The opt-programs.htop.settings option is introduced to
+
    • The programs.htop.settings option is introduced to
 replace individual options in programs.htop. To migrate, set the
-htop options directly in opt-programs.htop.settings. For
+htop options directly in programs.htop.settings. For
 example:
      programs.htop = {
   enabled = true;
   settings = {
@@ -314,21 +314,21 @@ changes are only active if the home.stateVersion op
 2020.
       
        
         
          
           Highlights   
        
       
      This release has the following notable changes:
      • Nothing has happened.
      
 
       
        
         
          
           State Version Changes   
        
       
      The state version in this release includes the changes below. These
 changes are only active if the home.stateVersion option is set to
-"20.09" or later.
      
 
-
       
        
         
          
           Release 20.03   
        
       
       
      Table of Contents
       
        
         Highlights 
         State Version Changes 
       
      The 20.03 release branch became the stable branch in April, 2020.
       
        
         
          
           Highlights   
        
       
      This release has the following notable changes:
       
        
         
          
           Release 20.03   
        
       
       
      Table of Contents
       
        
         Highlights 
         State Version Changes 
       
      The 20.03 release branch became the stable branch in April, 2020.
       
        
         
          
           Highlights   
        
       
      This release has the following notable changes:
      • Assigning a list to the home.file,
+xdg.dataFile options is
 now deprecated and will produce a warning message if used.
 Specifically, if your configuration currently contains something
 like
        home.file = [
@@ -403,7 +403,7 @@ assignment inside a config attribute. For example,
 
      • The services.compton module has been deprecated and instead the
 new module services.picom should be used. This is because Nixpkgs
 no longer packages compton, and instead packages the (mostly)
-compatible fork called picom.
      • The list form of the opt-programs.ssh.matchBlocks option has
+compatible fork called picom.
      • The list form of the programs.ssh.matchBlocks option has
 been deprecated and configurations requiring match blocks in a
 defined order should switch to using DAG entries instead. For
 example, a configuration
        programs.ssh.matchBlocks = [
@@ -428,7 +428,7 @@ example, a configuration
        programs.ssh.
 20.09.
      
 
       
        
         
          
           State Version Changes   
        
       
      The state version in this release includes the changes below. These
 changes are only active if the home.stateVersion option is set to
-"20.03" or later.
      • The opt-programs.zsh.history.path option is no longer
+"20.03" or later.
        • The programs.zsh.history.path option is no longer
 prepended by $HOME, which allows specifying absolute paths, for
 example, using the xdg module. Also, the default value is fixed to
 $HOME/.zsh_history and dotDir path is not prepended to it
@@ -444,19 +444,19 @@ can be used to uninstall Home Manager, if used in the standalone
 mode. That is, not as a NixOS module.
        
 
       
        
         
          
           State Version Changes   
        
       
      The state version in this release includes the changes below. These
 changes are only active if the home.stateVersion option is set to
-"19.09" or later.
      
 
-
       
        
         
          
           Release 19.03   
        
       
       
      Table of Contents
       
        
         Highlights 
         State Version Changes 
       
      The 19.03 release branch became the stable branch in April, 2019.
       
        
         
          
           Highlights   
        
       
      This release has the following notable changes:
       
        
         
          
           Release 19.03   
        
       
       
      Table of Contents
       
        
         Highlights 
         State Version Changes 
       
      The 19.03 release branch became the stable branch in April, 2019.
       
        
         
          
           Highlights   
        
       
      This release has the following notable changes:
      • The home.file.name.source option now allows source
 files to be hidden, that is, having a name starting with the .
 character. It also allows the source file name to contain characters
 not typically allowed for Nix store paths. For example, your
 configuration can now contain things such as
        home.file."my file".source = ./. + "/file with spaces!";
 
      • The type used for the systemd unit options under
-opt-systemd.user.sockets,
+systemd.user.sockets,
 etc. has been changed to offer more robust merging of
 configurations. If you don’t override values within systemd units
 then you are not affected by this change. Unfortunately, if you do
@@ -468,10 +468,10 @@ function. For example,
        systemd.user.se
 
        We had to make this change because the old merging was causing too
 many confusing situations for people.
      
 
       
        
         
          
           State Version Changes   
        
       
      The state version in this release includes the changes below. These
-changes are only active if the opt-home.stateVersion option is
-set to “19.03” or later.
      
 
      
 
 
       
        
         
          
           Release 18.09   
        
       
      The 18.09 release branch became the stable branch in September, 2018.