From: Adrian Bunk <bunk@stusta.de>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>,
openembedded-architecture
<openembedded-architecture@lists.openembedded.org>
Subject: Re: [Openembedded-architecture] Future of sato and X in oe-core
Date: Wed, 12 Feb 2020 13:40:18 +0200 [thread overview]
Message-ID: <20200212114018.GA4081@localhost> (raw)
In-Reply-To: <CANNYZj_JXMzwQuLcUwfAty_ESZZ8gWav+K9_gz8dDqSZR+xUEw@mail.gmail.com>
On Tue, Feb 11, 2020 at 07:06:57PM +0100, Alexander Kanavin wrote:
> On Tue, 11 Feb 2020 at 18:53, Richard Purdie <
> richard.purdie@linuxfoundation.org> wrote:
>
> > I still strongly believe we need something in core which pulls together
> > all our pieces into a UI where you can test key elements of what we
> > build. If we don't have sato how do we actually test the core or demo
> > it?
>
> See my other email I just wrote; I think epiphany/webkit under weston is
> able to replace sato more or less fully in this aspect,
Regarding dependencies and buildtime, epiphany/webkit is the largest
part of sato.
If you anyways want core to ship all the multimedia libraries and
ruby and rust and plenty of other packages, then an additional
desktop environment in core would be relatively lightweight.
A small core would be headless.
> and actually do
> more when it comes to modern embedded UI use cases which involve video and
> 3D.
>...
epiphany/webkit is a strange option to support in core for that,
moving Qt back into core instead would bring more usage in actual
products instead of shipping test/demo-only software.
> Alex
cu
Adrian
prev parent reply other threads:[~2020-02-12 11:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-11 12:49 Future of sato and X in oe-core Alexander Kanavin
2020-02-11 13:53 ` [Openembedded-architecture] " Adrian Bunk
2020-02-11 13:57 ` Alexander Kanavin
2020-02-11 14:01 ` Alexander Kanavin
2020-02-11 14:13 ` Adrian Bunk
2020-02-11 14:35 ` Alexander Kanavin
2020-02-11 15:02 ` Adrian Bunk
2020-02-11 15:58 ` Mark Hatle
2020-02-11 17:46 ` Alexander Kanavin
2020-02-16 16:38 ` Alexander Kanavin
2020-02-11 15:54 ` Mark Hatle
2020-02-11 14:05 ` Josef Holzmayr
2020-02-11 17:53 ` Richard Purdie
2020-02-11 17:59 ` Martin Jansa
2020-02-11 18:06 ` Alexander Kanavin
2020-02-12 11:40 ` Adrian Bunk [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=20200212114018.GA4081@localhost \
--to=bunk@stusta.de \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-architecture@lists.openembedded.org \
--cc=openembedded-core@lists.openembedded.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