Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-architecture
	<openembedded-architecture@lists.openembedded.org>,
	OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [Openembedded-architecture] Future of sato and X in oe-core
Date: Tue, 11 Feb 2020 17:02:12 +0200	[thread overview]
Message-ID: <20200211150212.GC3234@localhost> (raw)
In-Reply-To: <CANNYZj_2WVWrWDbL1tsUeqVQ_OPHnzebA=6fobRD9e==UybAhA@mail.gmail.com>

On Tue, Feb 11, 2020 at 03:35:03PM +0100, Alexander Kanavin wrote:
> X might and likely will start to bitrot sooner for those not using RHEL 8
> and its very conservative and never changing software stack. I can imagine
> Red Hat has no interest in supporting it on Fedora going forward for
> instance, they'll just make Xwayland work, and rip the standalone server
> and its drivers and libraries out.

There are plenty of other users big and small left, and most of the
hardware support already moved to the kernel.

Stale and stable is not necessarily bad for users, and X will not
suddenly stop working.

> Oe-core will have X for as long as the burden of fixing build errors and
> runtime issues with custom patches is not too painful.

If this is true, then let's revisit this topic in 10 years.

And the solution would then likely be to switch from matchbox/sato
to some desktop environment that supports wayland.

> The point I am
> trying to make is that I am not convinced oe-core needs a 'real' ui at all,
> and opinion to the contrary should justify the need.

The point I am trying to make is that this is a different discussion.

And any "no UI in oe-core" decision would not have to wait until the 
point in the distant future when X might no longer be supportable.

> Alex

cu
Adrian


  reply	other threads:[~2020-02-11 15:02 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 [this message]
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

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=20200211150212.GC3234@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