[oe] ANNOUNCEMENT: meta-python2 has been created

[Martin Jansa]

On Tue, Dec 03, 2019 at 12:26:44PM +0100, Martin Jansa wrote:
> On Mon, Dec 02, 2019 at 08:10:17PM -0800, Tim Orling wrote:
> > On Mon, Dec 2, 2019 at 8:07 AM Martin Jansa <martin.jansa at gmail.com> wrote:
> > 
> > > Thanks
> > >
> > > It would be nice to delete all branches except master. Only master branch
> > > makes sense now for meta-python2, right?
> > >
> > > " The stable branches were also kept, to make it easier to refer back to
> > prior history
> > and allow developers to use meta-python2 only in their workflow."
> > 
> > I can see use cases where a developer may want to replace meta-python with
> > meta-python2 and still be on a "stable" release. It also makes reviewing
> > what existed in which release much easier with cgit or git log --oneline,
> > which I do VERY frequently. If this is contentious then the OE-TSC will
> > make the decision.
> 
> But python2 is still in oe-core zeus and older so it should continue to
> be maintained there, right?
> 
> Why should people add meta-python2 to zeus (or older) builds? If there
> are more security updates to python2 or any other recipes, then they
> should still land in oe-core or meta-oe/meta-python as well and
> maintaining the duplicates in meta-python2 seems unnecessary overhead.
> 
> My understanding was that meta-python2 is just to help transition from
> oe-core/master when the python2 is dropped there.

I have to take this back (partially).

There are some python2 recipes which were already removed from zeus,
e.g. python-numpy:
http://git.openembedded.org/openembedded-core/commit/?h=zeus&id=4e9659f24e2f699effadcbe378b6a746d77ccdbd
python-nose:
http://git.openembedded.org/openembedded-core/commit/?h=zeus&id=9f07b2836405d86e869780f8f1ae00843eadc409

I've noticed these 2, because they are used by catkin and rospy in meta-ros

But I still don't feel well including this whole layer which duplicates
many recipes from oe-core/zeus or meta-oe/zeus just for these 2 recipes
(and making meta-python2 mandatory for every meta-ros/zeus user), so
I'll probably just import them to meta-ros.

Also neither of these is included in meta-python2, so it wouldn't help
in my use-case and before understanding what the zeus branch is for I
don't want to send patches to add them.

Or can you please explain what's the advantage of using
meta-python2/zeus? I mean including it in a build (not just for git
log).

On another topic, there is the compatibility issue caused by
python/python2 being removed from HOSTTOOLS in:
http://git.openembedded.org/openembedded-core/commit/?id=5f8f16b17f66966ae91aeabc23e97de5ecd17447

Is this something meta-python2 should help with the transition as well
or should we leave that to distro maintainers? Khem already fixed few
qt* recipes in meta-qt5 to use python3, but that's only in master branch
and people who might want to use newer oe-core with older meta-qt5 (e.g.
5.12 LTS version) will need to work-around this as well.

But I understand that changing HOSTTOOLS in meta-python2/conf/layer.conf
is quite controversial as it has bigger side-effect than just making
bunch of recipes available.

Regards,
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://lists.openembedded.org/pipermail/openembedded-devel/attachments/20191211/0667070b/attachment.sig>