From: Luca Boccassi <luca.boccassi@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v3] python*-setuptools: add separate packages for pkg_resources module
Date: Tue, 21 May 2019 13:35:22 +0100 [thread overview]
Message-ID: <3824e96c3c191f5df0432ef98b0c210312ea0e78.camel@gmail.com> (raw)
In-Reply-To: <20190521123418.16290-1-luca.boccassi@gmail.com>
On Tue, 2019-05-21 at 13:34 +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
> >
> ---
>
> v2: restrict new RDEPENDS to class-target. As advised by Alexander,
> bitbake
> cannot resolve native rdeps that mention package names rather
> than
> recipe names.
> v3: manually add RPROVIDES to the native class instead of restricting
> the
> RDEPENDS to the target class as a better workaround. Also
> document why
> the package is being split.
>
> meta/recipes-devtools/python/python-setuptools.inc | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/meta/recipes-devtools/python/python-setuptools.inc
> b/meta/recipes-devtools/python/python-setuptools.inc
> index 357aa07086..f49e078697 100644
> --- a/meta/recipes-devtools/python/python-setuptools.inc
> +++ b/meta/recipes-devtools/python/python-setuptools.inc
> @@ -37,3 +37,14 @@ do_install_prepend() {
> }
>
> BBCLASSEXTEND = "native nativesdk"
> +
> +# The pkg-resources module can be used by itself, without the
> package downloader
> +# and easy_install. Ship it in a separate package so that it can be
> used by
> +# minimal distributions.
> +PACKAGES =+ "${PYTHON_PN}-pkg-resources "
> +FILES_${PYTHON_PN}-pkg-resources =
> "${PYTHON_SITEPACKAGES_DIR}/pkg_resources/*"
> +# Due to the way OE-Core implemented native recipes, the native
> class cannot
> +# have a dependency on something that is not a recipe name. Work
> around that by
> +# manually setting RPROVIDES.
> +RDEPENDS_${PN}_append = " ${PYTHON_PN}-pkg-resources"
> +RPROVIDES_append_class-native = " ${PYTHON_PN}-pkg-resources-native"
>
Sorry, wrong in-reply-to, resending.
--
Kind regards,
Luca Boccassi
prev parent reply other threads:[~2019-05-21 12:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 21:40 [PATCH] systemd: enable portabled by default and install utilities in systemd-container luca.boccassi
2019-05-10 5:23 ` Martin Hundebøll
2019-05-10 10:45 ` Luca Boccassi
2019-05-10 10:46 ` Martin Hundebøll
2019-05-10 12:09 ` [PATCH v2] systemd: enable portabled by default luca.boccassi
2019-05-10 16:45 ` Khem Raj
2019-05-13 10:10 ` Luca Boccassi
2019-05-13 15:24 ` Khem Raj
2019-05-14 22:08 ` Luca Boccassi
2019-05-21 12:34 ` [PATCH v3] python*-setuptools: add separate packages for pkg_resources module luca.boccassi
2019-05-21 12:35 ` Luca Boccassi [this message]
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=3824e96c3c191f5df0432ef98b0c210312ea0e78.camel@gmail.com \
--to=luca.boccassi@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox