From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: elogind system-sleep scripts location documentation issue
Date: Mon, 28 Nov 2022 18:28:00 +0100 [thread overview]
Message-ID: <20221128172800.qWQsrLDkMWXG-UjX1F22EhCV--Muou44535949zolgE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40824@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1044 bytes --]
New comment by paper42 on void-packages repository
https://github.com/void-linux/void-packages/issues/40824#issuecomment-1329473660
Comment:
The [logind.conf(5)](https://man.voidlinux.org/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.
prev parent reply other threads:[~2022-11-28 17:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 17:04 [ISSUE] " rubin55
2022-11-28 17:28 ` paper42 [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221128172800.qWQsrLDkMWXG-UjX1F22EhCV--Muou44535949zolgE@z \
--to=paper42@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).