From: camoz <camoz@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Why does `elogind` not depend on `dbus-elogind` but `dbus`?
Date: Thu, 23 Dec 2021 07:55:17 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34675@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 359 bytes --]
New issue by camoz on void-packages repository
https://github.com/void-linux/void-packages/issues/34675
Description:
Hi,
I noticed that the package `elogind` does not depend on `dbus-elogind` but `dbus`. Is there a specific reason for this? (I'm new to non-systemd distros so I'm just learning the relationships between those things etc...)
Thanks.
next reply other threads:[~2021-12-23 6:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-23 6:55 camoz [this message]
2022-06-20 2:13 ` github-actions
2022-06-20 12:08 ` camoz
2022-06-20 13:19 ` Duncaen
2022-09-19 2:14 ` github-actions
2022-10-04 2:13 ` [ISSUE] [CLOSED] " github-actions
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34675@inbox.vuxu.org \
--to=camoz@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).