foodogsquared/nixos-config
1
0
Fork 0
mirror of https://github.com/foo-dogsquared/nixos-config.git synced 2025-02-24 18:19:01 +00:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

chore: update notes for gnome-session

Browse Source
This commit is contained in:
Gabriel Arazas 2024-01-21 20:12:51 +08:00
parent 8134ff798f
commit 5232684467
No known key found for this signature in database
GPG Key ID: ADE0C41DAB221FCC
1 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
modules/nixos/programs/gnome-session/submodules.nix
View File

@ -265,12 +265,19 @@ rec {
know how different desktop components interact with each other know how different desktop components interact with each other
especially if one of them failed. especially if one of them failed.
* Even if we have a way to limit starting desktop components with
`systemd-xdg-autostart-condition`, using `Service.ExecCondition=`
would severely limit possible reuse of desktop components with other
NixOS-module-generated gnome-session sessions so we're not bothering
with those.
TODO: Is `Type=notify` a good default? TODO: Is `Type=notify` a good default?
* `Service.Type=` is obviously not included since not all desktop * `Service.Type=` is obviously not included since not all desktop
components are the same either. Some of them could a D-Bus service, components are the same either. Some of them could a D-Bus service,
some of them are oneshots, etc. Not to mention, this is already implied some of them are oneshots, etc. Not to mention, this is already implied
to be `Type=simple` by systemd anyways. to be `Type=simple` by systemd anyways.
TODO: A good balance for this value, probably?
* `Service.OOMScoreAdjust=` have different values for different * `Service.OOMScoreAdjust=` have different values for different
components so it isn't included. components so it isn't included.