From: nonchip <nonchip@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: elogind systemd dependencies
Date: Fri, 06 Nov 2020 19:14:44 +0100 [thread overview]
Message-ID: <20201106181444.2KNAeq9OBxT9cpGP4ZLAO7Os47T0zE9oW0GdqPqB-W0@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: 936 bytes --]
New comment by nonchip on void-packages repository
https://github.com/void-linux/void-packages/issues/26177#issuecomment-723226023
Comment:
i see 3 issues with this issue:
* the `elogind` package doesn't actually depend on `systemd` at all
* github uses markdown, not bbcode, please use ``` instead of `[code]` and `[/code]`
* and nothing in that `post_install` function you're quoting actually introduces any dependency on systemd, the name is simply there for compatibility with software that expects there to be a systemd-logind under that name.
essentially the same as `libressl` installing `/usr/bin/openssl` as a compatibility wrapper. that doesn't mean it "depends on" `openssl`, on the contrary it allows other things to *not* depend on it. same applies here, due to the compatibility stuff installed by `elogind` we make it so we don't have to install systemd-logind but still support software that's "used to" that.
next prev parent reply other threads:[~2020-11-06 18: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 [this message]
2020-11-06 18:16 ` nonchip
2020-11-06 18:20 ` nonchip
2020-11-06 18:22 ` nonchip
2020-11-06 22:14 ` [ISSUE] [CLOSED] " q66
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=20201106181444.2KNAeq9OBxT9cpGP4ZLAO7Os47T0zE9oW0GdqPqB-W0@z \
--to=nonchip@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).