elogind system-sleep scripts location documentation issue

[rubin55]

Is this a new report?

Yes

System Info

Void 6.0.10_1 x86_64 AuthenticAMD uptodate rrmFFFF

Package(s) Affected

elogind-246.10_2

Does a report exist for this bug with the project's home (upstream) and/or another distro?

No, it's Void Linux specific.

Expected behaviour

Void (correctly!) configures /etc/elogind/system-sleep as the location for suspend/hibernate pre/post scripts. However, documentation does not indicate this. Upstream docs reference /lib64/elogind/system-sleep as the location. This leads to confusion with users.

I think /etc/elogind/system-sleep is correct, however Void docs should have a mention about this location.

Actual behaviour

N/A, issue made by request of @paper42 (paper_ on irc).

Steps to reproduce

1. install elogind
2. try to place a script in /usr/lib/elogind/system-sleep
3. observe it not working
4. place script in /etc/elogind/system-sleep
5. it works
6. wish for better docs

[paper42]

The logind.conf(5) manpage mentions both /lib/elogind/system-sleep and /etc/elogind/system-sleep, but the /lib/elogind/system-sleep path is incorrect, currently it should be /usr/libexec/elogind/system-sleep.

This is because we set -Drootlibexecdir=/usr/libexec/elogind and the build system uses

systemshutdowndir = join_paths(rootlibexecdir, 'system-shutdown')
systemsleepdir = join_paths(rootlibexecdir, 'system-sleep')

If we didn't set rootlibexecdir, it would default to /lib/elogind and this wouldn't be an issue.

a) the documentation should be adjusted
b) systemsleepdir and systemshutdowndir should be patched
c) rootlibexecdir should be changed (this would probably affect more than just this)

Alpine uses the same rootlibexecdir as we do, so they probably have the same issue, Gentoo uses /usr/lib/elogind.