-
-
Notifications
You must be signed in to change notification settings - Fork 14.6k
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/sway: Extend the default configuration for NixOS #122605
nixos/sway: Extend the default configuration for NixOS #122605
Conversation
The default config.in template contains "include @sysconfdir@/sway/config.d/*" but we've dropped it to better support non-NixOS (which seems like a mistake in retrospect). This restores that behaviour and extends the default configuration via nixos.conf to fix NixOS#119445. Note: The security configurations (security.d) where dropped entirely (but maybe they'll return).
Some resources regarding this:
|
I just tested this with a default configuration and @GrahamcOfBorg test sway |
Result of 4 packages built successfully:
3 suggestions:
Result of 4 packages built successfully:
3 suggestions:
|
Let's merge this for NixOS 21.05. Having |
This test is important to confirm that $WAYLAND_DISPLAY is correctly imported via "dbus-update-activation-environment --systemd" which is done by default since NixOS#122605 (00e8e5b). It ensures that the gnome3-pinentry pop-ups work as expected to avoid regressions like NixOS#119445 (which also broke screen sharing).
i'm not clear on how adding stuff to the default config is "restoring behaviour" |
@evils that part's a bit complicated due to NixOS vs. Nix outside of NixOS, Nix store paths (that get garbage collected), and copying Sway's default configuration file (which should not contain any Nix store paths that will get GCed). Together with the Git history that hopefully explains the reasoning at the time. https://github.com/NixOS/nixpkgs/pull/122995/files#diff-635aedb425667b0a9cd9ecab374760ed0c32a1853a15e95d5fb86cdfc047da1f might also help explaining it. |
Idk if this is linked but now when I run |
@NilsIrl huh, that sounds very strange (unless you're SSHing to your own machine and the same user). Shouldn't be related though (and it's easy to test). I quickly tested running |
It seems to me that this is what I'm doing? I'm SSHing into the machine that is running sway as the user that is running sway (the user account I use for everything) |
The default config.in template contains
"include @sysconfdir@/sway/config.d/*" but we've dropped it to better
support non-NixOS (which seems like a mistake in retrospect).
This restores that behaviour and extends the default configuration via
nixos.conf to fix #119445.
Note: The security configurations (security.d) where dropped entirely
(but maybe they'll return).
Motivation for this change
Note: This is currently just an idea/draft and I haven't tested it yet. Unfortunately it's somewhat hacky so an alternative would be to drop our support to easily use our Sway package outside of NixOS (we could ask around if anyone uses that and if it even works as expected).
TODOs: Extend the NixOS VM test for Sway to test pinentry (maybe an optional test/extension if this causes too many rebuilds when testing changes to core packages).
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)