[OE-core] [PATCH 0/3] Restructure python2 and python3 packaging system

Richard Purdie richard.purdie at linuxfoundation.org
Fri Aug 18 11:37:05 UTC 2017


On Fri, 2017-08-18 at 12:33 +0100, Richard Purdie wrote:
> On Fri, 2017-08-18 at 11:23 +0100, Richard Purdie wrote:
> > 
> > On Thu, 2017-08-17 at 10:11 -0700, Alejandro Hernandez wrote:
> > > 
> > > 
> > > The reason we have a manifest file for python is that our goal is
> > > to
> > > keep python-core as small as posible and add other python
> > > packages
> > > only when the user needs them, hence why we split upstream python
> > > into several packages.
> > > 
> > > There are many problems with our current implementation of the
> > > manifest file, this patch tries to deal with all of them along
> > > with
> > > adding several other features.
> > > 
> > > This patch adds a new task to python recipes, which is meant to
> > > create a new manifest file every release.
> > https://autobuilder.yocto.io/builders/build-appliance/builds/416/steps/BuildImages_1/logs/stdio
> https://autobuilder.yocto.io/builders/nightly-packagemanagers/builds/68/steps/Running%20Sanity%20Tests/logs/stdio
> 
> (no fcntl module)

https://autobuilder.yocto.io/builders/buildtools/builds/409/steps/BuildImages/logs/stdio

Cheers,

Richard





More information about the Openembedded-core mailing list