Martin Gaens: I have a home-manager config which is either managed on its own or within NixOS, which I use across 2 different computer. I am using the extraSpecialArgs in flake.nix or home-manager.users.nicolas._module.args when embedded in a NixOS configuration, to set some configuration managed externally.

Note, there is nothing about special args, I might have as well set an option by adding an extra module in homeManager's flake.nix and done the same within the configuration embedded in NixOS.

I can either use my home manager as a standalone entry in my flake.nix:

    homeConfigurations.nicolas = home-manager.lib.homeManagerConfiguration {
      extraSpecialArgs = inputs // {
        inNixOS = false;
      };
      pkgs = import nixpkgs-unstable {
        system = "x86_64-linux";
        overlays = [ self.overlays.openpnp ];
      };
      modules = [ ./users/nicolas/home.nix ];
    };

Or as a module to import in my NixOS configuration:

{ home-manager, ...}@inputs:

{
  imports = [
    home-manager.nixosModules.home-manager
  ];

  home-manager = {
    users.nicolas.imports = [ ./home.nix ];
    users.nicolas._module.args = {
      inNixOS = true;
    } // inputs;
  };
}

The inNixOS argument is nothing special, this is just an extra attribute I give as argument to the home-manager modules to tune it differently.

I can either use my home manager as a standalone entry in my flake.nix:

    homeConfigurations.nicolas = home-manager.lib.homeManagerConfiguration {
      extraSpecialArgs = inputs // {
        inNixOS = false;
      };
      pkgs = import nixpkgs-unstable { system = "x86_64-linux"; };
      modules = [ ./users/nicolas/home.nix ];
    };

Or as a module to import in my NixOS configuration:

{ home-manager, ...}@inputs:

{
  imports = [
    home-manager.nixosModules.home-manager
  ];

  home-manager = {
    users.nicolas.imports = [ ./home.nix ];
    users.nicolas._module.args = {
      inNixOS = true;
    } // inputs;
  };
}

The inNixOS argument is nothing special, this is just an extra attribute I give as argument to the home-manager modules to tune it differently.

I can either use my home manager as a standalone entry in my flake.nix:

    homeConfigurations.nicolas = home-manager.lib.homeManagerConfiguration {
      extraSpecialArgs = inputs // {
        inNixOS = false;
      };
      pkgs = import nixpkgs-unstable { system = "x86_64-linux"; };
      modules = [ ./users/nicolas/home.nix ];
    };

Or as a module to import in my NixOS configuration:

{ home-manager, ...}@inputs:

{
  imports = [
    home-manager.nixosModules.home-manager
  ];

  home-manager = {
    users.nicolas.imports = [ ./home.nix ];
    users.nicolas._module.args = {
      inNixOS = true;
      inherit (inputs) awesome-copycats; // list other inputs forwarded from NixOS to home-manager
    };
  };
}

The inNixOS argument is nothing special, this is just an extra attribute I give as argument to the home-manager modules to tune it differently.

I can either use my home manager as a standalone entry in my flake.nix:

    homeConfigurations.nicolas = home-manager.lib.homeManagerConfiguration {
      extraSpecialArgs = inputs // {
        inNixOS = false;
      };
      pkgs = import nixpkgs-unstable { system = "x86_64-linux"; };
      modules = [ ./users/nicolas/home.nix ];
    };

Or as a module to import in my NixOS configuration:

{ home-manager, ...}@inputs:

{
  imports = [
    home-manager.nixosModules.home-manager
  ];

  home-manager = {
    users.nicolas.imports = [ ./home.nix ];
    users.nicolas._module.args = {
      inNixOS = true;
      inherit (inputs) awesome-copycats; # list other inputs forwarded from NixOS to home-manager
    };
  };
}

The inNixOS argument is nothing special, this is just an extra attribute I give as argument to the home-manager modules to tune it differently.

I can either use my home manager as a standalone entry in my flake.nix:

    homeConfigurations.nicolas = home-manager.lib.homeManagerConfiguration {
      extraSpecialArgs = inputs // {
        inNixOS = false;
      };
      pkgs = import nixpkgs-unstable { system = "x86_64-linux"; };
      modules = [ ./home.nix ];
    };

Or as a module to import in my NixOS configuration:

{ home-manager, ...}@inputs:

{
  imports = [
    home-manager.nixosModules.home-manager
  ];

  home-manager = {
    users.nicolas.imports = [ ./home.nix ];
    users.nicolas._module.args = {
      inNixOS = true;
      inherit (inputs) awesome-copycats; # list other inputs forwarded from NixOS to home-manager
    };
  };
}

The inNixOS argument is nothing special, this is just an extra attribute I give as argument to the home-manager modules to tune it differently.

I already asked in https://matrix.to/#/!6oudZq5zJjAyrxL2uY:0upti.me/$7AxNR83n3qUrjad6j0KXIDLtaUKnZIxy-sP_liLL04A, but this might be a better place:

I have written 1x module, and I want to make use of it (read: extend it) in another .nix file.

The module I have written looks like this:

{ lib, ... }:
{
  options.flake.modules.foo = lib.mkOption {
    type =
      with lib.types;
      attrsOf (
        submodule (
          { name, ... }:
          {
            options = {
              username = lib.mkOption {
                type = str;
                default = lib.splitString "@" name |> lib.flip builtins.elemAt 0;
              };
              hostname = lib.mkOption {
                type = str;
                default = lib.splitString "@" name |> lib.flip builtins.elemAt 1;
              };
              system = lib.mkOption {
                type = enum [
                  "x86_64-linux"
                ];
              };
            };
          }
        )
      );
  };
  config.flake.modules.foo."username@hostname".system = "x86_64-linux";
}

Now I want to extend foo like this:

{
  lib,
  repoRoot,
  ...
}@toplevel:
let
  fooConfs = toplevel.config.flake.modules.foo;
in
{
  options.flake.modules.foo.<fooInstance>.home-manager = lib.mkOption {
    type =
      with lib.types;
      attrsOf (
        submodule (
          {
            name,
            config,
            ...
          }:
          let
            username = config.username;
            hostname = config.hostname;
            system = config.system;
          in
          {
            entryPoint = lib.mkOption {
              type = lib.types.path;
              default = "${repoRoot}/home-manager/${username}@${hostname}";
            };
            homeDirectory = lib.mkOption {
              type = lib.types.path;
              default =
                if lib.strings.hasSuffix "-darwin" system then "/Users/${username}" else "/home/${username}";
            };
            toplevelBuild = lib.mkOption {
              type = lib.types.raw;
              readOnly = true;
            };
          }
        )
      );
  };
  config.flake.modules.foo.<fooInstance>.home-manager = fooConfs;
}

I have obviously grossly misunderstood something, so anyone here got any suggestions on how to proceed?

BTW: I'm not even sure I want homeManager to be nested under flake.modules.foo, I'd be happier if it was alongside like so flake.modules.homeManager.<instance of home-manager generated from instance of foo>

In reply to @n4ch723hr3r:nope.chat
i think you have to overwrite the type if that is possible

In reply to @n4ch723hr3r:nope.chat
from what i understand about the module system everything inside attrsOf is a subtype so you have to find a way to put something new into that type

In reply to @n4ch723hr3r:nope.chat
from what i understand about the module system everything inside attrsOf is a subtype so you have to find a way to put something new into that type

    users.users = lib.mkOption {
      type = with lib.types; attrsOf (submodule userOptions);
    };

found this in the openssh module