I've got some questions for everyone:

• What's your biggest painpoints using NixOS &/ home-manager today?

Mine's still packaging things that doesn't quite fit the "norm". (https://github.com/dawsers/hyprscroller comes to mind right now).

I've got some questions for everyone:

• What's your biggest painpoints using NixOS &/ home-manager today?
• What package update solution are you using to update your own derivations?

Mine's still packaging things that doesn't quite fit the "norm". (https://github.com/dawsers/hyprscroller comes to mind right now).

In reply to @erinvanderveen:matrix.org
I used the nixpkgs function to create Hyprland plugins

In reply to @erinvanderveen:matrix.org
I used the nixpkgs function to create Hyprland plugins

In reply to @lillecarl:matrix.org
What's the purpose of the setattr and getattr for namespace? Looks a bit overcomplicated for my eyes

writing it that adds the module to a namespace of your choice (replace namespace) , so you dont have to add it manually in every module. Looking into it we realised there might be more readable ways to set it, but for now it works.

The way we get the filename doesnt though. Ill get an update on the final result

In reply to @lillecarl:matrix.org

I've got some questions for everyone:

• What's your biggest painpoints using NixOS &/ home-manager today?
• What package update solution are you using to update your own derivations?

Mine's still packaging things that doesn't quite fit the "norm". (https://github.com/dawsers/hyprscroller comes to mind right now).

  hyprscroller = pkgs.unstable.hyprlandPlugins.mkHyprlandPlugin pkgs.hyprland {
    pluginName = "hyprscroller";
    version = pkgs.hyprland.version; # No version present in repo, just use hyprland version instead

    src = inputs.hyprscroller;

    installPhase = ''
      mkdir -p $out/lib/
      cp hyprscroller.so $out/lib/libhyprscroller.so
    '';

    dontStrip = true;

    nativeBuildInputs = with pkgs; [ cmake ];

    meta = with pkgs.lib; {
      homepage = "https://github.com/dawsers/hyprscroller";
      description = "Hyprland layout plugin providing a scrolling layout like PaperWM";
      license = licenses.mit;
      platforms = platforms.linux;
      maintainers = [ maintainers.erin ];
    };
  };

In reply to @erinvanderveen:matrix.org

  hyprscroller = pkgs.unstable.hyprlandPlugins.mkHyprlandPlugin pkgs.hyprland {
    pluginName = "hyprscroller";
    version = pkgs.hyprland.version; # No version present in repo, just use hyprland version instead

    src = inputs.hyprscroller;

    installPhase = ''
      mkdir -p $out/lib/
      cp hyprscroller.so $out/lib/libhyprscroller.so
    '';

    dontStrip = true;

    nativeBuildInputs = with pkgs; [ cmake ];

    meta = with pkgs.lib; {
      homepage = "https://github.com/dawsers/hyprscroller";
      description = "Hyprland layout plugin providing a scrolling layout like PaperWM";
      license = licenses.mit;
      platforms = platforms.linux;
      maintainers = [ maintainers.erin ];
    };
  };

In reply to @erinvanderveen:matrix.org

https://nix-community.github.io/home-manager/options.xhtml#opt-wayland.windowManager.hyprland.plugins

Home Manager already has a way to add plugins. No need to make that module yourself 😉

In reply to @lillecarl:matrix.org
Aah, so the intention is creation options that align with the file path?

Final template. Reading a filename elegantly isn't supported by the builtins, the nameBaseOf returns the current dir-name so we reorganized to a folder structure supporting it (and more future proof anyway)

{ config, lib, pkgs, ... }:

let
  name = baseNameOf ./.;
  cfg = lib.getAttr name config.oatmeal;
in
{
  imports = [
  ];

  options.oatmeal.${name} = with lib; {
    enable = mkEnableOption (name + " module");
  };

  config = {
  };
}

In reply to @lillecarl:matrix.org
Aah, so the intention is creation options that align with the file path?

Don't know what __curPos, looks cursed 😄
Final template. Reading a filename elegantly isn't supported by the builtins, the nameBaseOf returns the current dir-name so we reorganized to a folder structure supporting it (and more future proof anyway)

{ config, lib, pkgs, ... }:

let
  name = baseNameOf ./.;
  cfg = lib.getAttr name config.oatmeal;
in
{
  imports = [
  ];

  options.oatmeal.${name} = with lib; {
    enable = mkEnableOption (name + " module");
  };

  config = {
  };
}

{ config, inputs, secrets, lib, pkgs, ... }:

let
  cfg = config.oatmeal;
  dir-content = builtins.readDir ./.;
in
{
  imports = lib.filter lib.isPath (lib.forEach (lib.attrNames dir-content) (key: if (lib.getAttr key dir-content) == "directory" then (./. + ("/" + key)) else null )) ++ \[
  \];

  options.oatmeal = with lib; {
    users = mkOption {
      type = types.listOf types.str;
    };
  };

  config = {
    home-manager = {
      extraSpecialArgs = { inherit inputs secrets; };
      users =
        lib.foldl'
          (acc: user: { "${user}" = import (../../users + ("/" + user + "/home.nix")); } // acc)
          {}
          cfg.users;
    };
 };
}

Module importer/scheduler also got a glow-up, pulling in all modules dynamically from the path.

The single import line is pretty macho though, but I'm pretty happy with it after I figured it out.

{ config, inputs, secrets, lib, pkgs, ... }:

let
  cfg = config.oatmeal;
  dir-content = builtins.readDir ./.;
in
{
  imports = lib.filter lib.isPath (lib.forEach (lib.attrNames dir-content) (key: if (lib.getAttr key dir-content) == "directory" then (./. + ("/" + key)) else null )) ++ \[
  \];

  options.oatmeal = with lib; {
    users = mkOption {
      type = types.listOf types.str;
    };
  };

  config = {
    home-manager = {
      extraSpecialArgs = { inherit inputs secrets; };
      users =
        lib.foldl'
          (acc: user: { "${user}" = import (../../users + ("/" + user + "/home.nix")); } // acc)
          {}
          cfg.users;
    };
 };
}

In reply to @alxplus:matrix.org
Thanks! Speaking of pain points before, this is something I struggle with, trying to figure out what the most appropriate function, in the end whatever I do feels like a series of functions kept together by duct tape and a prayer 😅

Which is mostly correct I think XD

Functional programming has a tendency to feel like that. Especially Nix where there are no real types.