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
nixos/networkmanager: make basePackages configurable, rename packages… #140666
Conversation
type = types.listOf types.package; | ||
default = with pkgs; [ | ||
modemmanager | ||
networkmanager |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think networkmanager
should just always be included? Does it make sense to enable the module without including the base package?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe someone wants to override the package? but yeah, maybe we should do it some other way, but this was the least complex way I could think about
''; | ||
}; | ||
|
||
extraPackages = mkOption { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wait, now I got to this point and I'm a bit confused, why are all those plugins in the base instead of here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just for backwards compatibility. so people don't get missing packages if they don't change anything. the old packages option was really an extraPackages option and if we set a value here, it will override the default list.
The packages are also included in |
Also with that, there should not really be a need to distinguish the base and extra packages. |
If I get this correctly, the passthru stuff should be added to each networkmanager package? I can try to do this also in this PR. |
Shouldn't this be an attrset? That way you can override specific packages. |
Yes, I would imagine something like
And the module would link those files.
That would be nice but I have not seen any standard for this to emerge so far. I think @infinisil was considering one? |
… to extraPackages
d21934e
to
d2aa259
Compare
Alright, I hope I did the right thing with the passthrus. Marked is as draft for now, until some (maybe me?) can test it on an actual system. Also I'm not sure if the split in basePackages + extraPackges is fine. Maybe we can write something in the release notes or add the packages depending on desktop environment so we have less complex code in the module. |
076144f
to
d2aa259
Compare
I have rebased this in #164531 and slightly changed. |
There's no established standard, but I think this is a good case where making this an attribute set is very beneficial. This way users can not only override plugins, but also remove them (by setting the attribute to |
Though I haven't looked into the backwards compatibility aspect of this, since there already is the existing |
A |
closing this in favor of #164531 which is a cleaner solution IMHO |
This pull request has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/networkmanager-plugins-installed-by-default/39682/8 |
… to extraPackages
Motivation for this change
alternate implementation of #84433
Things done
sandbox = true
set innix.conf
? (See Nix manual)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)