[Nix-dev] systemPackages vs. services.dbus.packages

[Mathijs Kwik]

Kirill Elagin <kirelagin at gmail.com> writes:

> On Tue, Apr 8, 2014 at 11:29 PM, Mathijs Kwik <mathijs at bluescreen303.nl>wrote:
>
>> I use that as much as possible.
>> There's really no need for a lot of packages to be in systemPackages or
>> in some user profile if they only provide a service and don't have lots
>> of often-used CLI tools. Same goes for udevPackages.
>>
>
> How exactly do you use that? I mean, there are _exactly two_ NixOS modules
> that add some packages to `dbus.packages` but do not add those same packages
> to `systemPackages`.

Just put a package (like dunst) in dbus.packages without adding it to
systemPackages. I'm not talking about modules here.

On another system, I mkForce systemPackages, essentially removing stuff
that gets added by default by modules and provide everything I do need
manually. This can indeed be a bit cumbersome, but it really keeps the
system profile clean. The fact that a system is running a database or
webserver should not mean every user gets to see its binaries in their
path.

>
> % grep -Rl 'dbus\.packages' | xargs grep -L 'systemPackages'
> modules/services/x11/display-managers/lightdm.nix
> modules/services/x11/desktop-managers/e17.nix