diff --git a/index.xhtml b/index.xhtml index 81822142c..ba28afad5 100644 --- a/index.xhtml +++ b/index.xhtml @@ -85,7 +85,7 @@ Nix option. On NixOS you can control this option using the system option.

  • Add the appropriate Home Manager channel. If you are following Nixpkgs master or an unstable channel you can run

    $ nix-channel --add https://github.com/nix-community/home-manager/archive/master.tar.gz home-manager
     $ nix-channel --update
    -

    and if you follow a Nixpkgs version 24.05 channel you can run

    $ nix-channel --add https://github.com/nix-community/home-manager/archive/release-24.05.tar.gz home-manager
    +

    and if you follow a Nixpkgs version 24.11 channel you can run

    $ nix-channel --add https://github.com/nix-community/home-manager/archive/release-24.11.tar.gz home-manager
     $ nix-channel --update
     
  • Run the Home Manager installation command and create the first Home Manager generation:

    $ nix-shell '<home-manager>' -A install
    @@ -114,7 +114,7 @@ your system configuration. This is most conveniently done by adding a
     Home Manager channel to the root user. For example, if you are following
     Nixpkgs master or an unstable channel, you can run

    $ sudo nix-channel --add https://github.com/nix-community/home-manager/archive/master.tar.gz home-manager
     $ sudo nix-channel --update
    -

    and if you follow a Nixpkgs version 24.05 channel, you can run

    $ sudo nix-channel --add https://github.com/nix-community/home-manager/archive/release-24.05.tar.gz home-manager
    +

    and if you follow a Nixpkgs version 24.11 channel, you can run

    $ sudo nix-channel --add https://github.com/nix-community/home-manager/archive/release-24.11.tar.gz home-manager
     $ sudo nix-channel --update
     

    It is then possible to add

    imports = [ <home-manager/nixos> ];
     

    to your system configuration.nix file, which will introduce a new @@ -126,7 +126,7 @@ home-manager.users.eve = { pkgs, ... }: { # The state version is required and should stay at the version you # originally installed. - home.stateVersion = "24.05"; + home.stateVersion = "24.11"; };

    and after a sudo nixos-rebuild switch the user eve’s environment should include a basic Bash configuration and the packages atool and @@ -165,7 +165,7 @@ your system configuration. This is most conveniently done by adding a Home Manager channel. For example, if you are following Nixpkgs master or an unstable channel, you can run

    $ nix-channel --add https://github.com/nix-community/home-manager/archive/master.tar.gz home-manager
     $ nix-channel --update
    -

    and if you follow a Nixpkgs version 24.05 channel, you can run

    $ nix-channel --add https://github.com/nix-community/home-manager/archive/release-24.05.tar.gz home-manager
    +

    and if you follow a Nixpkgs version 24.11 channel, you can run

    $ nix-channel --add https://github.com/nix-community/home-manager/archive/release-24.11.tar.gz home-manager
     $ nix-channel --update
     

    It is then possible to add

    imports = [ <home-manager/nix-darwin> ];
     

    to your nix-darwin configuration.nix file, which will introduce a new @@ -180,7 +180,7 @@ home-manager.users.eve = { pkgs, ... }: { # The state version is required and should stay at the version you # originally installed. - home.stateVersion = "24.05"; + home.stateVersion = "24.11"; };

    and after a darwin-rebuild switch the user eve’s environment should include a basic Bash configuration and the packages atool and httpie.

    If you do not plan on having Home Manager manage your shell @@ -252,7 +252,7 @@ command performs a combined build and activation.

    { config, pkgs, ... }:
       # You can update Home Manager without changing this value. See
       # the Home Manager release notes for a list of state version
       # changes in each release.
    -  home.stateVersion = "24.05";
    +  home.stateVersion = "24.11";
     
       # Let Home Manager install and manage itself.
       programs.home-manager.enable = true;
    @@ -467,14 +467,14 @@ introduction about writing a Home Manager configuration.

  • user, you can run the Home Manager init command directly from its flake.

    For example, if you are using the unstable version of Nixpkgs or NixOS, then to generate and activate a basic configuration run the command

    $ nix run home-manager/master -- init --switch
    -

    For Nixpkgs or NixOS version 24.05 run

    $ nix run home-manager/release-24.05 -- init --switch
    +

    For Nixpkgs or NixOS version 24.11 run

    $ nix run home-manager/release-24.11 -- init --switch
     

    This will generate a flake.nix and a home.nix file in ~/.config/home-manager, creating the directory if it does not exist.

    If you omit the --switch option then the activation will not happen. This is useful if you want to inspect and edit the configuration before activating it.

    $ nix run home-manager/$branch -- init
     $ # Edit files in ~/.config/home-manager
     $ nix run home-manager/$branch -- init --switch
    -

    Where $branch is one of master or release-24.05.

    After the initial activation has completed successfully then building +

    Where $branch is one of master or release-24.11.

    After the initial activation has completed successfully then building and activating your flake-based configuration is as simple as

    $ home-manager switch
     

    It is possible to override the default configuration directory, if you want. For example,

    $ nix run home-manager/$branch -- init --switch ~/hmconf
    diff --git a/release-notes.xhtml b/release-notes.xhtml
    index 99f09d7a0..3964454fc 100644
    --- a/release-notes.xhtml
    +++ b/release-notes.xhtml
    @@ -32,8 +32,7 @@ changes are only active if the home.stateVersion op
     "25.05" or later.

    • No changes.

    -

    Release 24.11

    Table of Contents

    Highlights
    State Version Changes

    This is the current unstable branch and the information in this section -is therefore not final.

    Highlights

    This release has the following notable changes:

    • The swayidle module behavior has changed. Specifically, swayidle was +

    Release 24.11

    Table of Contents

    Highlights
    State Version Changes

    The 24.05 release branch became stable in November, 2024.

    Highlights

    This release has the following notable changes:

    • The swayidle module behavior has changed. Specifically, swayidle was previously always called with a -w flag. This flag is now moved to the default services.swayidle.extraArgs @@ -46,7 +45,7 @@ future removal. The new value for true is false it is null.

    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 -"24.11" or later.

    • No changes.

    +"24.11" or later.

    • There was no state version change in this release.

    Release 24.05

    Table of Contents

    Highlights
    State Version Changes

    The 24.05 release branch became stable in May, 2024.

    Highlights

    This release has the following notable changes:

    • The .release file in the Home Manager project root has been