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).
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).
Changes bootstrap script to run libtoolize. Some extra magic was needed for
autoreconf (taken from GNOME projects).
The INTLTOOL_DESKTOP_RULE should be used in Makefile.am but is unfortunately
broken at this time for out-of-source builds. The rule is instead copied and
fixed in Makefile.am.
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.
This is primarily for improved discovery. Some users report that they didn't know about redshift-gtk, but had it been available on tab completion they would have noticed. Also, I think it is in general good practice that closely related programs have the same prefix.
Hugo Osvaldo Barrera