redshift-ng/data/systemd, branch master

Cleanup

2025-03-24T06:12:22Z

systemd services are removed as they are fundamentally flawed Signed-off-by: Mattias Andrée

Change services to by wanted by graphical-session

2020-06-14T09:31:42Z

The previous value (`default.target`) meant that redshift got started when a user session began, at which point we can't expect a graphic session to be up and running (eg: Xorg or Wayland may have not even been invoked yet). Setting `WantedBy=graphical-session.target` ensures that, when the service is enable, it'll only get run when starting a graphical session (again, either Xorg or Wayland, whatever DE's may be used).

Set redshift to run after graphical-sesion.target

2020-06-14T09:31:42Z

The previous reference (`display-manager.service`) is not something that's included with systemd. While it may be present on some user's system (because they created it, or some specific package includes it), it can't be expected to be present. On the other hand, `graphical-session.target` is included with systemd, and can be expected to be there, and be triggered when starting a graphical session. This guarantees that redshift will only run AFTER a graphic session is up (eg: either Xorg or Wayland are up).

Add systemd user unit file for redshift-gtk

2014-03-20T16:27:00Z

Add systemd .service file for redshift

2014-03-20T16:27:00Z

Add a systemd user .service file to allow users to run redshift as a daemon using systemd. Also adds a new configure option, `--with-systemduserunitdir`, which gives the install path. If set to `no`, systemd support is disabled. If not set, we use `pkg-config` to find the path.