-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[feature request] mark own modules as not imported by default #115
Comments
iirc you can use systems.hosts.my-host.modules = with inputs; [
# my-input.nixosModules.my-module
]; to make specific systems import a module |
wait you're already using that 🥴 |
Yes, what I want to do is to make it so that |
you could try - although it would be a bit awkward - to move the module to a separate repo and import from there |
I would like to be able to mark certain modules defined in my flake as not imported to all systems by default.
Currently, I have a module that configures a buildbot-nix worker. However, this means that I also have to add
buildbot-nix.nixosModules.buildbot-worker
tosystems.modules.nixos
so that all systems pick it up. This increases evaluation time and is also a lot "dirtier" in terms of what I'm importing, since most machines will not have the buildbot worker on them. Therefore, if I could mark a module as non-importable somehow, I could make it so that only machines that will run a worker will import this, and by extension, also the buildbot-worker module from buildbot-nix. Is this possible at all with snowfall?The text was updated successfully, but these errors were encountered: