From: flexibeast <flexibeast@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: sddm requires `xorg-server` as a dependency
Date: Wed, 13 May 2020 06:00:22 +0200 [thread overview]
Message-ID: <20200513040022.ePUv8AR2vZza1X9lglcgh2HjapcaRmtmlG6iAeGGvww@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21862@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1125 bytes --]
New comment by flexibeast on void-packages repository
https://github.com/void-linux/void-packages/issues/21862#issuecomment-627722248
Comment:
Well, i've been spending hours in VMs trying to work out what packages users need when trying to use DEs, for the purposes of the documentation i'm writing for the Handbook. Regardless of whether SDDM *should* have a hard dependency on `xorg-server`, my testing showed that it currently does - without `xorg-server` installed, SDDM simply doesn't work. Once SDDM is started, one can certainly choose a Wayland-based Plasma session, but that involves getting SDDM started in the first place. It's true that a particular setup might involve an X server running on another machine, but i doubt that's the most common use case for KDE users.
i'm opposed to 'fixing' this sort of issue via documentation. If something is a soft dependency, sure, let's note that in documentation. But for hard dependencies like this, i feel that either the `sddm` package should be modified to depend on `xorg-server`, or that work is done by upstream so that this dependency is no longer required.
next prev parent reply other threads:[~2020-05-13 4:00 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 5:40 [ISSUE] " flexibeast
2020-05-12 7:23 ` ericonr
2020-05-13 0:14 ` sgn
2020-05-13 0:37 ` ericonr
2020-05-13 0:48 ` fosslinux
2020-05-13 0:52 ` sgn
2020-05-13 1:44 ` fosslinux
2020-05-13 3:26 ` flexibeast
2020-05-13 4:00 ` flexibeast [this message]
2020-05-13 4:02 ` flexibeast
2020-05-13 12:03 ` sgn
2020-05-14 0:05 ` fosslinux
2020-05-14 0:32 ` flexibeast
2020-05-14 4:00 ` fosslinux
2020-05-14 4:25 ` flexibeast
2020-05-14 4:27 ` fosslinux
2020-05-14 4:37 ` flexibeast
2020-05-14 4:37 ` flexibeast
2020-05-14 6:15 ` fosslinux
2020-05-14 7:31 ` pullmoll
2020-05-14 7:32 ` pullmoll
2020-05-14 8:31 ` flexibeast
2020-05-14 8:55 ` pullmoll
2020-05-14 9:26 ` flexibeast
2020-05-15 10:10 ` Anachron
2020-05-15 10:46 ` flexibeast
2020-05-15 12:04 ` flexibeast
2020-05-15 14:46 ` not-chicken
2020-05-18 2:51 ` the-maldridge
2020-05-18 2:51 ` [ISSUE] [CLOSED] " the-maldridge
2020-05-18 2:52 ` flexibeast
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=20200513040022.ePUv8AR2vZza1X9lglcgh2HjapcaRmtmlG6iAeGGvww@z \
--to=flexibeast@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).