Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/weston: add option to build seatd-based launcher
Date: Sat, 6 Aug 2022 15:39:24 +0200	[thread overview]
Message-ID: <20220806153924.2cb54040@windsurf> (raw)
In-Reply-To: <20220805165705.GH3621445@scaer>

Hello,

On Fri, 5 Aug 2022 18:57:05 +0200
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:

> On 2022-08-04 22:46 +0200, Thomas Petazzoni via buildroot spake thusly:
> > Since version 10, the weston-launch command has been deprecated, and
> > can only be built with -Ddeprecated-weston-launch=true, which
> > Buildroot does not do.
> > 
> > So the only launcher currently available is logind, provided by
> > systemd.  
> 
> Forgot to add in my previous reply...
> 
> Is a launcher mandatory? Should we en sure that at least one is present?
> I.e. if dbus+systemd is not set, then select seatd?

I am not 100% clear on this. My current understanding is indeed that a
launcher is needed.

However, it would be possible to use the logind launcher with elogind,
which is Gentoo's extract of logind from systemd as a standalone
project: https://wiki.gentoo.org/wiki/Elogind. Of course, we don't
currently have elogind as a Buildroot package.

The options would be:

 - logind launcher, with systemd
 - logind launcher, with elogind
 - libseat launcher, with seatd

Best regards,

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-08-06 13:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-04 20:46 [Buildroot] [PATCH] package/weston: add option to build seatd-based launcher Thomas Petazzoni via buildroot
2022-08-05 16:53 ` Yann E. MORIN
2022-08-05 16:57 ` Yann E. MORIN
2022-08-06 13:39   ` Thomas Petazzoni via buildroot [this message]
2022-08-08 16:56     ` Arnout Vandecappelle

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=20220806153924.2cb54040@windsurf \
    --to=buildroot@buildroot.org \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yann.morin.1998@free.fr \
    /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