don't re-instantiate nixpkgs in flake and module

[getchoo]

This is expensive on evaluation, but can be easily avoided here as we aren't using unfree packages or special configurations

See https://zimbatm.com/notes/1000-instances-of-nixpkgs

The only systems this will affect are those not listed here, as the overlay will no longer be automatically applied and an assertion will be triggered. They will need to add nixpkgs.overlays = [ comin.overlays.default ] to their configuration; users on other systems will have overlayed packages used by default as well

[nlewo]

Hello,
The CI fails because you added an option without running nix run .#generate-module-options to regenerate the markdown file describing the options.

So, you need to

• run nix run .#generate-module-options
• commit markdown file modifications

[getchoo]

Done!

I've updated the Nixpkgs revision as well, since it seems it was still on the now EOL 24.05 branch. nix flake check worked on x86_64-linux

[nlewo]

Thank you!

[nlewo]

hm, looks like i merged it a bit too quickly: it no longer evaluates on my machines:

       error: attribute 'packages' missing
       at /nix/store/4ipj96bhdy4wh6c4fxqik4kd05knkm1m-source/nix/module.nix:26:71:
           25|       # If the package is null and our `system` isn't supported by the Flake, it's probably safe to show this error message
           26|       { assertion = package == null -> lib.elem system (lib.attrNames self.packages); message = "comin: ${system} is not supported by the Flake."; }
             |                                                                       ^
           27|     ];

No time ATM to fix this.

[getchoo]

I believe this line is the culprit

self: should be { self }: