In reply to @mib:kanp.ai

do you actually want to refer to your lib or die you mean to import it first?

if import, then just import it in a let in and pass it to both your modules and lib. something like

outputs = { self, nixpkgs }: let
    lib = import ./lib;
in {
  nixosModules = rec {
    myModule = import ./nixos { inherit lib; };
    default = myModule;
  };
  inherit lib;
}

In reply to @crtified:crtified.me
Or you use self.lib in the module

In reply to @mib:kanp.ai

do you actually want to refer to your lib or die you mean to import it first?

if import, then just import it in a let in and pass it to both your modules and lib. something like

outputs = { self, nixpkgs }: let
    lib = import ./lib;
in {
  nixosModules = rec {
    myModule = import ./nixos { inherit lib; };
    default = myModule;
  };
  inherit lib;
}

In reply to @crtified:crtified.me
https://gist.github.com/CRTified/69f83b3c1eef037413a400566e583cd3 Note that the externalModule.nix contains a function taking self which returns the usual module (which is a function in config, lib, ...)

In reply to @janik0:matrix.org
thank you for this ❤️

In reply to @crtified:crtified.me
Oh, if you need the proper name for that concept: It's a Closure - more obvious with the external module

In reply to @janik0:matrix.org
I'll look into that later. I gave myself the challenge of getting a deeper understating of the nix lang and nixos module system so I'm Implementing a dns libary a module which gives necessary meta information to generate something like a octodns config.

In reply to @janik0:matrix.org
I think this works, but I also need pass in the nixpkgs lib and the magic nixosModules config attribute somehow

In reply to @crtified:crtified.me
https://gist.github.com/CRTified/69f83b3c1eef037413a400566e583cd3

In reply to @crtified:crtified.me
Oh, if you need the proper name for that concept: It's a Closure - more obvious with the external module

In reply to @mib:kanp.ai
Nice idea! I hope you share it once you're done! :)

In reply to @janik0:matrix.org
I would try to avoid anything relying on a extra piece of infrastructure that is potentially a single point of failure so the whole proxy thing seems quite meh I find the approach https://github.com/snowfallorg/thaw is taking nice but I have to admit I didn't use it yet.

In reply to @antifuchs:asf.computer
Ooooh, that does look pretty excellent! I’m skeptical of the proxy approach too, and I even more dislike having transitive deps inject those into my system dependencies… so today I switched from Eza to lsd (: