From: Tim Orling <ticotimo@gmail.com>
To: alex.kanavin@gmail.com
Cc: Martin Jansa <martin.jansa@gmail.com>,
peter.marko@siemens.com, "marex@denx.de" <marex@denx.de>,
"openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>
Subject: Re: [oe] [meta-python2][PATCH] layer.conf: update LAYERSERIES_COMPAT for scarthgap
Date: Wed, 17 Apr 2024 06:59:00 -0700 [thread overview]
Message-ID: <CANx9H-CXeVm5Hq=uuANL_vsSAvKfUzjMZU_q74Dx3xQ=DrRxjA@mail.gmail.com> (raw)
In-Reply-To: <CANNYZj-AXRhPc+ak1TjfF01B06217T9gQ_1Bn5JCVrxZF44MnA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2320 bytes --]
On Wed, Apr 17, 2024 at 2:00 AM Alexander Kanavin via lists.openembedded.org
<alex.kanavin=gmail.com@lists.openembedded.org> wrote:
> On Tue, 16 Apr 2024 at 17:03, Martin Jansa <martin.jansa@gmail.com> wrote:
> > As there is strong opinion against declaring scarthgap compatibility
> > in official meta-python2 from Timo, Alex and Jose, I don't plan to
> > merge Marek's change (nor my version with additional fixes for
> > Upstream-Status etc).
>
> There's more to it. It's a protest against people focusing on obsolete
> retro computing stuff because of their poor product planning, while
> offering no help to keep things current. It took me two months to
> update python to 3.12 while ensuring nothing breaks in core or
> meta-oe. Something you Marek perhaps don't need right now, but will
> certainly need in the future. Did you help?
>
To echo what Alex is saying here (I have spent months of my life,
uncompensated for the effort, to bring the pyproject.toml and
other new PEP-517 build backend classes into oe-core, with a lot of very
hard effort from RP and Ross).
In addition, with my OpenEmbedded Board member hat on and my OpenEmbedded
TSC member hat on, I take this
stance:
We as an organization in no way whatsoever want anyone to think it is ok to
continue to use python2. You have had well over a
decade of warning and foreshadowing. The licensing probably means we do not
have any actual legal liability exposure, but in
our modern litigious society, this is no guarantee. You have had two years
of kirkstone support and still have two more years before
kirkstone is EOL. This is the end of the line. This is where this stops.
Plan your way out of this situation and move on.
Tim
We cannot control what users and companies want to bring into their own
layers. They are welcome to at their
>
> Alex
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#110039):
> https://lists.openembedded.org/g/openembedded-devel/message/110039
> Mute This Topic: https://lists.openembedded.org/mt/105535514/924729
> Group Owner: openembedded-devel+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub [
> ticotimo@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>
[-- Attachment #2: Type: text/html, Size: 3555 bytes --]
prev parent reply other threads:[~2024-04-17 13:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 13:14 [meta-python2][PATCH] layer.conf: update LAYERSERIES_COMPAT for scarthgap Marek Vasut
2024-04-15 13:49 ` [oe] " Jose Quaresma
2024-04-15 13:58 ` Marek Vasut
2024-04-15 15:20 ` Tim Orling
2024-04-15 17:17 ` Alexander Kanavin
2024-04-15 17:48 ` Martin Jansa
2024-04-16 13:55 ` Marek Vasut
2024-04-16 14:17 ` [oe] " Alexander Kanavin
2024-04-16 14:19 ` Marko, Peter
2024-04-16 14:27 ` Alexander Kanavin
2024-04-16 15:03 ` Martin Jansa
2024-04-17 9:00 ` Alexander Kanavin
2024-04-17 13:59 ` Tim Orling [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='CANx9H-CXeVm5Hq=uuANL_vsSAvKfUzjMZU_q74Dx3xQ=DrRxjA@mail.gmail.com' \
--to=ticotimo@gmail.com \
--cc=alex.kanavin@gmail.com \
--cc=marex@denx.de \
--cc=martin.jansa@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=peter.marko@siemens.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).