From: ifreund <ifreund@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: seatd-0.4.0
Date: Fri, 30 Oct 2020 13:03:33 +0100 [thread overview]
Message-ID: <20201030120333.pd3IUvPn7Pl1i2bOPjsnUDr58T7QNvYkwhR6xSJFfb4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24580@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 907 bytes --]
New comment by ifreund on void-packages repository
https://github.com/void-linux/void-packages/pull/24580#issuecomment-719484859
Comment:
> Not sure if I misunderstood anything, but wouldn't it be better to separate libseat from seatd and make seatd depend on it? This way when wlroots with libseat support gets released (it's already implemented in master), it could be compiled with libseat support instead of elogind and depend on libseat.
`libseat` is separated from seatd, but seatd doesn't depend on it. `seatd` is a standalone daemon while `libseat` is a library for programs such as a wayland compositor to interact with that daemon (and optionally logind as well).
When the next wlroots version is released it will indeed depend on libseat by default, though I'm not sure we should remove `elogind` dependence by default just yet. These decisions can be exposed as build options of course.
next prev parent reply other threads:[~2020-10-30 12:03 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-31 14:53 [PR PATCH] New package: seatd-0.2.0 ifreund
2020-08-31 15:04 ` [PR REVIEW] " ericonr
2020-08-31 15:04 ` ericonr
2020-08-31 15:04 ` ericonr
2020-08-31 15:04 ` ericonr
2020-08-31 15:04 ` ericonr
2020-08-31 15:04 ` ericonr
2020-08-31 15:53 ` ifreund
2020-08-31 15:54 ` ifreund
2020-08-31 15:57 ` ifreund
2020-08-31 15:58 ` [PR PATCH] [Updated] " ifreund
2020-08-31 16:32 ` [PR REVIEW] " ericonr
2020-08-31 16:32 ` ericonr
2020-08-31 16:33 ` ericonr
2020-08-31 16:48 ` ericonr
2020-08-31 16:48 ` [PR REVIEW] " ifreund
2020-08-31 17:56 ` [PR PATCH] [Updated] " ifreund
2020-08-31 17:57 ` ifreund
2020-09-08 11:20 ` [PR PATCH] [Updated] " ifreund
2020-09-08 11:27 ` New package: seatd-0.3.0 ifreund
2020-09-08 11:32 ` [PR REVIEW] " ericonr
2020-09-08 11:32 ` ericonr
2020-09-08 12:15 ` [PR PATCH] [Updated] " ifreund
2020-09-08 12:16 ` [PR REVIEW] " ifreund
2020-10-21 11:30 ` [PR PATCH] [Updated] " ifreund
2020-10-21 11:30 ` ifreund
2020-10-21 11:54 ` [PR REVIEW] " Duncaen
2020-10-21 12:12 ` ifreund
2020-10-21 12:27 ` [PR REVIEW] New package: seatd-0.4.0 Duncaen
2020-10-21 12:48 ` [PR PATCH] [Updated] " ifreund
2020-10-21 12:52 ` [PR REVIEW] " ifreund
2020-10-30 10:38 ` ofiala-a51
2020-10-30 10:41 ` ofiala-a51
2020-10-30 10:56 ` ifreund
2020-10-30 11:15 ` ofiala-a51
2020-10-30 11:58 ` ifreund
2020-10-30 12:03 ` ifreund [this message]
2020-10-30 12:12 ` ofiala-a51
2020-10-30 12:12 ` ofiala-a51
2020-11-08 15:06 ` [PR REVIEW] " ofiala-a51
2020-11-08 15:06 ` ofiala-a51
2020-11-08 15:07 ` ofiala-a51
2020-11-08 16:52 ` ofiala-a51
2020-11-08 22:22 ` ifreund
2020-11-08 22:25 ` Duncaen
2020-11-08 22:28 ` ifreund
2020-11-08 22:30 ` [PR PATCH] [Updated] " ifreund
2020-11-08 22:43 ` [PR REVIEW] " ifreund
2020-11-10 20:50 ` ofiala-a51
2020-11-10 21:07 ` [PR PATCH] [Updated] " ifreund
2020-11-10 21:17 ` [PR REVIEW] " PaperMountainStudio
2020-11-10 21:18 ` PaperMountainStudio
2020-11-17 0:50 ` ericonr
2020-11-17 9:44 ` ifreund
2020-11-17 18:27 ` [PR PATCH] [Merged]: " ericonr
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=20201030120333.pd3IUvPn7Pl1i2bOPjsnUDr58T7QNvYkwhR6xSJFfb4@z \
--to=ifreund@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).