From: "Khem Raj" <raj.khem@gmail.com>
To: Martin Jansa <Martin.Jansa@gmail.com>, Tim Orling <ticotimo@gmail.com>
Cc: Yocto-mailing-list <yocto@lists.yoctoproject.org>,
openembedded-core <openembedded-core@lists.openembedded.org>,
"openembedded-devel@lists.openembedded.org"
<Openembedded-devel@lists.openembedded.org>
Subject: Re: [yocto] [OE-core] Let me tell you how I really feel. Zero filter. If you need meta-python2, you need to become a maintainer. Immediately. Period.
Date: Thu, 22 Oct 2020 14:39:37 -0700 [thread overview]
Message-ID: <dedefa25-3055-0d7c-973b-4200f3c58ef3@gmail.com> (raw)
In-Reply-To: <CA+chaQfL9RtRiJYph7=yGxMrgoiOPRovdfJOPf524vXY-bD7aQ@mail.gmail.com>
On 10/22/20 2:36 PM, Martin Jansa wrote:
> There were only a few changes needed between dunfell and gatesgarth to
> keep it building and I feel guilty for sending half of them - and
> pinging you on FB :).
>
> I don't have interest in python2, but it's still used by quite a few
> components included in other layers are care about (e.g. qtwebengine in
> meta-qt5, chromium in meta-browser -
> https://bugs.chromium.org/p/chromium/issues/detail?id=942720
> <https://bugs.chromium.org/p/chromium/issues/detail?id=942720> is still
> quite far from finished) and at LGE we maintain meta-ros
> https://github.com/ros/meta-ros <https://github.com/ros/meta-ros> which
> contains support for ROS 1 Melodic which is usually used with python2
> and support ends May 2023 (together with Ubuntu Bionic it's usually used
> with: http://wiki.ros.org/Distributions
> <http://wiki.ros.org/Distributions> - just today I've separated
> meta-ros-python2 layer with python2 recipes which disappeared from
> oe-core in warrior and were never re-introduced in meta-python2 (like
> nose and numpy).
>
> If you're looking for someone just keeping it buildable, then you can
> sign me up. If it gets more annoying to maintain in future we can also
> split it for pythonnative.bbclass and python recipe itself - to keep
> just the bare minimum of recipes which are actively being used without
> all the other junk.
minimum is better.
>
> Cheers,
>
> On Wed, Oct 21, 2020 at 2:48 AM Tim Orling <ticotimo@gmail.com
> <mailto:ticotimo@gmail.com>> wrote:
>
> I have absolutely no need for python2, I made this abundantly clear
> when I created the meta-python2 layer.
>
> If you depend upon continuing support of python2 via the
> meta-python2 layer, this is your call to arms.
>
> I was originally intending to abdicate any support after the 3.1
> "dunfell" release, but managed to somehow continue supporting it
> into the crest of the 3.2 "gatesgarth" release.
>
> I will stop all support and actively refuse lo respond to any emails
> and this layer will be dead and I have zero care in the world that
> it stops being useful. I do not use it. I do not depend upon it. You
> are not paying me to do this. You cannot pay me enough to do this.
> Period. Support yourself.
>
> If this is not clear enough, I am happy to have a virtual video call
> with you that you will not like.
>
> --moto-timo
>
>
>
>
>
>
>
next prev parent reply other threads:[~2020-10-22 21:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-21 0:48 Let me tell you how I really feel. Zero filter. If you need meta-python2, you need to become a maintainer. Immediately. Period Tim Orling
2020-10-22 21:36 ` [OE-core] " Martin Jansa
2020-10-22 21:39 ` Khem Raj [this message]
2020-10-24 10:53 ` [yocto] " Zoran
2020-10-24 11:19 ` Alexander Kanavin
[not found] ` <1640E842B1461A14.10923@lists.yoctoproject.org>
2020-10-24 17:38 ` Zoran
2020-10-24 20:22 ` Alexander Kanavin
2020-10-24 20:26 ` Zoran
2020-10-24 20:29 ` Alexander Kanavin
2020-10-24 21:51 ` [oe] " Alejandro Hernandez Samaniego
[not found] ` <16406E32EA0586FD.712@lists.yoctoproject.org>
2021-02-01 14:40 ` [yocto] [OE-core] " Martin Jansa
2021-02-01 23:19 ` Khem Raj
2021-02-02 9:33 ` Richard Purdie
2021-02-02 10:11 ` Zoran
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=dedefa25-3055-0d7c-973b-4200f3c58ef3@gmail.com \
--to=raj.khem@gmail.com \
--cc=Martin.Jansa@gmail.com \
--cc=Openembedded-devel@lists.openembedded.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=ticotimo@gmail.com \
--cc=yocto@lists.yoctoproject.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