From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/3] Restructure python2 and python3 packaging system
Date: Fri, 18 Aug 2017 12:33:45 +0100 [thread overview]
Message-ID: <1503056025.32591.10.camel@linuxfoundation.org> (raw)
In-Reply-To: <1503051783.32591.9.camel@linuxfoundation.org>
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)
Cheers,
Richard
next prev parent reply other threads:[~2017-08-18 11:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 17:11 [PATCH 0/3] Restructure python2 and python3 packaging system Alejandro Hernandez
2017-08-17 17:11 ` [PATCH 1/3] python: Restructure python packaging and replace it with autopackaging Alejandro Hernandez
2017-08-17 17:11 ` [PATCH 2/3] python3: fix RDEPENDS on several recipes, due to non-existent python3 packages Alejandro Hernandez
2017-08-17 17:11 ` [PATCH 3/3] python3: Restructure python3 packaging and replace it with autopackaging Alejandro Hernandez
2017-08-17 17:35 ` ✗ patchtest: failure for Restructure python2 and python3 packaging system Patchwork
2017-08-17 19:15 ` Alejandro Hernandez
2017-08-18 9:35 ` [PATCH 0/3] " Alexander Kanavin
2017-08-18 10:23 ` Richard Purdie
2017-08-18 11:33 ` Richard Purdie [this message]
2017-08-18 11:37 ` Richard Purdie
2017-08-23 13:46 ` Richard Purdie
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=1503056025.32591.10.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alejandro.hernandez@linux.intel.com \
--cc=openembedded-core@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.