From: Luca Boccassi <luca.boccassi@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] python*-setuptools: add separate packages for pkg_resources module
Date: Mon, 20 May 2019 16:04:52 +0100 [thread overview]
Message-ID: <9ca3cf5a62ce6c2aaee7e15b68be684184644200.camel@gmail.com> (raw)
In-Reply-To: <e8e8d3b516e2a0e3b30fe2aa1882700f3ad5df43.camel@linuxfoundation.org>
On Mon, 2019-05-20 at 15:14 +0100, Richard Purdie wrote:
> On Thu, 2019-05-16 at 22:09 +0100,
> luca.boccassi@gmail.com
> wrote:
> > From: Luca Boccassi <
> > luca.boccassi@microsoft.com
> > >
> >
> > The pkg_resources Python module is useful by itself, for example
> > for
> > automatic loading of resources shipped in a Python package.
> > Add separate packages for it, so that users can depend on them
> > individually and avoid pulling in the entire setuptools, which
> > include scripts to download other packages, which might not be
> > desired on minimal images.
> >
> > Other distributions like Debian and Ubuntu already split setuptools
> > and pkg-resources in this way.
> >
> > The setuptools packages now depend on the new pkg-resources
> > packages,
> > to avoid regressions for other packages that depend on them
> > already.
> >
> > Signed-off-by: Luca Boccassi <
> > luca.boccassi@microsoft.com
> > >
> > ---
> > meta/recipes-devtools/python/python-setuptools.inc | 4 ++++
> > 1 file changed, 4 insertions(+)
> >
> > diff --git a/meta/recipes-devtools/python/python-setuptools.inc
> > b/meta/recipes-devtools/python/python-setuptools.inc
> > index 357aa07086..ad00cbe0ef 100644
> > --- a/meta/recipes-devtools/python/python-setuptools.inc
> > +++ b/meta/recipes-devtools/python/python-setuptools.inc
> > @@ -24,6 +24,7 @@ RDEPENDS_${PN} = "\
> > ${PYTHON_PN}-html \
> > ${PYTHON_PN}-netserver \
> > ${PYTHON_PN}-numbers \
> > + ${PYTHON_PN}-pkg-resources \
> > ${PYTHON_PN}-pkgutil \
> > ${PYTHON_PN}-plistlib \
> > ${PYTHON_PN}-shell \
> > @@ -37,3 +38,6 @@ do_install_prepend() {
> > }
> >
> > BBCLASSEXTEND = "native nativesdk"
> > +
> > +PACKAGES =+ "${PYTHON_PN}-pkg-resources "
> > +FILES_${PYTHON_PN}-pkg-resources =
> > "${PYTHON_SITEPACKAGES_DIR}/pkg_resources/*"
>
>
> This breaks native builds:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/65/builds/614
>
>
> (and many other similar failures)
>
> Cheers,
>
> Richard
Hello Richard,
Thanks for the heads-up, any suggestion as to why the above patch
wouldn't be enough to build both native and target binary packages for $python-pkg-resources?
--
Kind regards,
Luca Boccassi
next prev parent reply other threads:[~2019-05-20 15:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 21:09 [PATCH] python*-setuptools: add separate packages for pkg_resources module luca.boccassi
2019-05-20 14:14 ` Richard Purdie
2019-05-20 15:04 ` Luca Boccassi [this message]
2019-05-20 16:28 ` Alexander Kanavin
2019-05-21 10:59 ` [PATCH v2] " luca.boccassi
2019-05-21 11:11 ` richard.purdie
2019-05-21 12:36 ` [PATCH v4] " luca.boccassi
2019-05-22 2:06 ` Khem Raj
2019-05-22 10:58 ` Luca Boccassi
2019-05-24 17:29 ` Khem Raj
2019-05-25 12:59 ` Luca Boccassi
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=9ca3cf5a62ce6c2aaee7e15b68be684184644200.camel@gmail.com \
--to=luca.boccassi@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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.