From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Remove packages `dbus-x11` and `dbus-elogind-x11`?
Date: Thu, 21 Jul 2022 04:14:53 +0200 [thread overview]
Message-ID: <20220721021453.r7LJdXXrcNhYyqZWsrOM5IL4evszxre5VfF6Lq7o1f0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34678@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 536 bytes --]
Closed issue by camoz on void-packages repository
https://github.com/void-linux/void-packages/issues/34678
Description:
The program `dbus-launch` along with its man page is split from `dbus` and `dbus-elogind` into `dbus-x11` and `dbus-elogind-x11`, respectively.
`dbus-launch` does not seem to be X11-specific though, it is just a "Utility to start a message bus from a shell script" (from the manpage). It can also be used with wayland compositors for example.
So, is the split really necessary? What advantages does it have?
prev parent reply other threads:[~2022-07-21 2:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-23 9:17 [ISSUE] " camoz
2022-04-07 14:46 ` atahanacar
2022-07-07 2:13 ` github-actions
2022-07-21 2:14 ` github-actions [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=20220721021453.r7LJdXXrcNhYyqZWsrOM5IL4evszxre5VfF6Lq7o1f0@z \
--to=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).