[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.


Martin Jansa
 

On Thu, Oct 22, 2020 at 11:37 PM Martin Jansa via lists.yoctoproject.org <Martin.Jansa=gmail.com@...> 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 is still quite far from finished) and at LGE we maintain 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 - 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.

Cheers,

Hi,

can I get the write access to meta-python2 as mentioned above?

I have 2 fixes to make it parse able with latest oe-core:

to fix issues discussed in:

Cheers,


Khem Raj
 



On Mon, Feb 1, 2021 at 6:40 AM Martin Jansa <Martin.Jansa@...> wrote:
On Thu, Oct 22, 2020 at 11:37 PM Martin Jansa via lists.yoctoproject.org <Martin.Jansa=gmail.com@...> 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 is still quite far from finished) and at LGE we maintain 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 - 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.

Cheers,

Hi,

can I get the write access to meta-python2 as mentioned above?

+1 





Richard Purdie
 

On Mon, 2021-02-01 at 15:40 +0100, Martin Jansa wrote:
can I get the write access to meta-python2 as mentioned above?

I have 2 fixes to make it parse able with latest oe-core:
https://lists.openembedded.org/g/openembedded-devel/message/89201
https://lists.openembedded.org/g/openembedded-devel/message/89200

to fix issues discussed in:
https://github.com/openembedded/openembedded-core/commit/fd6a007efa7cb45101a66f294af81d9d33bb3fab#commitcomment-46565284
https://lists.openembedded.org/g/openembedded-core/message/147477
https://lists.openembedded.org/g/openembedded-core/message/147514
This sounds like a good idea to me and I have admin right so I've given
you access :)

Cheers,

Richard


Zoran
 

This sounds like a good idea to me and I have admin
right so I've given you access :)
+1

Zee
_______

On Tue, Feb 2, 2021 at 10:33 AM Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:

On Mon, 2021-02-01 at 15:40 +0100, Martin Jansa wrote:
can I get the write access to meta-python2 as mentioned above?

I have 2 fixes to make it parse able with latest oe-core:
https://lists.openembedded.org/g/openembedded-devel/message/89201
https://lists.openembedded.org/g/openembedded-devel/message/89200

to fix issues discussed in:
https://github.com/openembedded/openembedded-core/commit/fd6a007efa7cb45101a66f294af81d9d33bb3fab#commitcomment-46565284
https://lists.openembedded.org/g/openembedded-core/message/147477
https://lists.openembedded.org/g/openembedded-core/message/147514
This sounds like a good idea to me and I have admin right so I've given
you access :)

Cheers,

Richard