From: q66 <q66@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] elogind systemd dependencies
Date: Fri, 06 Nov 2020 23:14:47 +0100 [thread overview]
Message-ID: <20201106221447.uNuev-0wT1-PeVC_Qd1uAs-fAx9HZhD7KBfAfjTKnT0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26177@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 967 bytes --]
Closed issue by dreamer1234 on void-packages repository
https://github.com/void-linux/void-packages/issues/26177
Description:
The elogind package is dependant on systemd.
Looking at the template:
[code]
post_install() {
ln -s libelogind.pc $DESTDIR/usr/lib/pkgconfig/libsystemd.pc
ln -s libelogind.pc $DESTDIR/usr/lib/pkgconfig/libsystemd-logind.pc
ln -sr $DESTDIR/usr/include/elogind $DESTDIR/usr/include/systemd
vinstall ./src/systemd/sd-id128.h 644 usr/include
vinstall ./src/systemd/_sd-common.h 644 usr/include
vinstall $FILESDIR/elogind.wrapper 755 usr/libexec/elogind
vmkdir usr/lib/dracut/dracut.conf.d
echo "install_items+=\" /usr/libexec/elogind/elogind-uaccess-command \"" >> ${DESTDIR}/usr/li
b/dracut/dracut.conf.d/elogind.conf
vsv elogind
}
[/code]
Which seems a bad desing, since we are introducing systemd dependencies on a non systemd distribution.
prev parent reply other threads:[~2020-11-06 22:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 16:54 [ISSUE] " dreamer1234
2020-11-06 18:08 ` ofiala-a51
2020-11-06 18:10 ` ofiala-a51
2020-11-06 18:14 ` nonchip
2020-11-06 18:16 ` nonchip
2020-11-06 18:20 ` nonchip
2020-11-06 18:22 ` nonchip
2020-11-06 22:14 ` q66 [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=20201106221447.uNuev-0wT1-PeVC_Qd1uAs-fAx9HZhD7KBfAfjTKnT0@z \
--to=q66@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).