On Thu, 2017-08-17 at 10:11 -0700, Alejandro Hernandez wrote:
> Alejandro Hernandez (3):
> python: Restructure python packaging and replace it with
> autopackaging
> python3: fix RDEPENDS on several recipes, due to non-existent
> python3
> packages
> python3: Restructure python3 packaging
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
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
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.
>
>
On 08/17/2017 08:11 PM, Alejandro Hernandez wrote:
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.
Thanks for doing this; does it mean that python 3.6 update is coming
soon? :)
A
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 f
