From: "Ludovic Courtès" <ludo@gnu.org>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: 40680@debbugs.gnu.org
Subject: [bug#40680] [PATCH] service: sddm: Have sddm-service-type conflict with other display managers.
Date: Sun, 19 Apr 2020 01:33:07 +0200 [thread overview]
Message-ID: <87h7xg4bf0.fsf@gnu.org> (raw)
In-Reply-To: <20200418180121.GA4725@E5400> (Efraim Flashner's message of "Sat, 18 Apr 2020 21:01:21 +0300")
Hi,
Efraim Flashner <efraim@flashner.co.il> skribis:
> On Fri, Apr 17, 2020 at 11:00:49PM +0200, Ludovic Courtès wrote:
[...]
>> > --- a/gnu/services/sddm.scm
>> > +++ b/gnu/services/sddm.scm
>> > @@ -171,6 +171,7 @@ Relogin=" (if (sddm-configuration-relogin? config)
>> > (documentation "SDDM display manager.")
>> > (requirement '(user-processes))
>> > (provision '(display-manager))
>> > + (conflicts-with '(xorg-server))
>>
>> ‘conflicts-with’ doesn’t exist, right? :-)
>>
>
> I haven't tried it out for Guix services, but it exists for shepherd
> services, according to the manual¹
Right, it’s not available in Guix <shepherd-service>.
However, simplify adding ‘xorg-server’ to ‘provision’ should have the
desired effect: ‘guix system’ errors out if more than one service
provides the same symbol.
>> But yes, I think (provision '(xorg-server display-manager)) would be
>> fine.
>>
>> Or we can even drop ‘display-manager’ since it’s not used anywhere else.
>
> Normally I'd be skeptical about dropping it since people might expect it
> if they're using sddm, but it'd probably be fine.
Yeah, maybe it’s safer to keep it.
Thanks,
Ludo’.
next prev parent reply other threads:[~2020-04-18 23:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 14:41 [bug#40680] [PATCH] service: sddm: Have sddm-service-type conflict with other display managers Efraim Flashner
2020-04-17 21:00 ` Ludovic Courtès
2020-04-18 18:01 ` Efraim Flashner
2020-04-18 23:33 ` Ludovic Courtès [this message]
2020-04-19 6:07 ` bug#40680: " Efraim Flashner
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h7xg4bf0.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=40680@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).