Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>,
	Ross Burton <Ross.Burton@arm.com>
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: RE: [OE-core] [PATCH 2/3] perf: make scripting depend on setuptools3
Date: Fri, 7 Oct 2022 15:00:00 +0000	[thread overview]
Message-ID: <cdcb6e0a62ca48dab8e2b288f542d956@axis.com> (raw)
In-Reply-To: <CADkTA4NsnL2CJ_wRVcwrOwSfWjuWD3gQ4esxrYaieOv1h_Bzrg@mail.gmail.com>

> -----Original Message-----
> From: openembedded-core@lists.openembedded.org <openembedded-
> core@lists.openembedded.org> On Behalf Of Bruce Ashfield
> Sent: den 6 oktober 2022 16:02
> To: Ross Burton <Ross.Burton@arm.com>
> Cc: Richard Purdie <richard.purdie@linuxfoundation.org>; openembedded-
> core@lists.openembedded.org
> Subject: Re: [OE-core] [PATCH 2/3] perf: make scripting depend on
> setuptools3
> 
> On Thu, Oct 6, 2022 at 9:43 AM Ross Burton <Ross.Burton@arm.com> wrote:
> >
> > On 6 Oct 2022, at 14:29, Bruce Ashfield <bruce.ashfield@gmail.com> wrote:
> > > I'm not particularly concerned if the extra RDEPENDS arrives with
> > > this, since if it is acceptable for other packages inheriting the
> > > setuptools (I thought it was build support only!), it really should be
> > > ok for perf as well. In particular since perf is debug/optional. Or am
> > > I missing something there ?
> >
> > With this change the base perf package will always runtime-depend on
> > python3, even if perf-python isn’t installed.  That sounds suboptimal.
> >
> 
> But is triggered on the 'scripting' packageconfig, which does mean we
> want the support, so it is at least somewhat conditional .. but yes, I
> agree that once we've built and packaged, it does make sense to keep
> the python dependencies in the dedicated package.
> 
> Let me re-work this and do the remove of the RDEPENDS and send a v2.
> 
> Bruce
> 
> > Ross

To me it sounds as what setuptools3-base.bbclass really should to is 
something like:

FOOBAR ??= "${PN}"
RDEPENDS:${FOOBAR}:append:class-target = " ${PYTHON_PN}-core"
...
FILES:${FOOBAR} += "${libdir}/* ${libdir}/${PYTHON_DIR}/*"

so that the typical Python only recipes continue to just inherit 
setuptools3, but recipes that produce other packages than the 
Python package can do something like:

FOOBAR = "${PYTHON_PN}-${PN}"

Unfortunately this does not work as it results in a gazillion 
warnings like:

WARNING: .../meta-oe/recipes-support/libiio/libiio_git.bb: Variable key FILES:${PN}-${PYTHON_PN} (${PYTHON_SITEPACKAGES_DIR}) replaces original key FILES:libiio-python3 ( ${libdir}/* ${libdir}/${PYTHON_DIR}/*).
WARNING: .../meta-oe/recipes-support/libiio/libiio_git.bb: Variable key RDEPENDS:${PN}-${PYTHON_PN} (${PN} ${PYTHON_PN}-ctypes ${PYTHON_PN}-stringold ${PYTHON_PN}-core) replaces original key RDEPENDS:libiio-python3 ( ${PYTHON_PN}-core).

(I chose libiio as it is an example of another recipes that currently 
does RDEPENDS:${PN}:remove = "${PYTHON_PN}-core" to counteract what 
setuptools3-base.bbclass does).

:(

//Peter


  reply	other threads:[~2022-10-07 15:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-04 17:27 [PATCH 0/3] kernel/kernel-yocto: 6.0 prep bruce.ashfield
2022-10-04 17:27 ` [PATCH 1/3] linux-yocto-dev: bump to v6.0+ bruce.ashfield
2022-10-04 17:27 ` [PATCH 2/3] perf: make scripting depend on setuptools3 bruce.ashfield
2022-10-06 11:28   ` [OE-core] " Ross Burton
2022-10-06 12:38     ` Bruce Ashfield
2022-10-06 13:13       ` Ross Burton
2022-10-06 13:29         ` Bruce Ashfield
2022-10-06 13:43           ` Ross Burton
2022-10-06 14:01             ` Bruce Ashfield
2022-10-07 15:00               ` Peter Kjellerstedt [this message]
2022-10-11  2:57                 ` Khem Raj
2022-10-11 11:54                   ` Bruce Ashfield
2022-10-04 17:27 ` [PATCH 3/3] lttng-modules: update to 2.13.7 bruce.ashfield

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=cdcb6e0a62ca48dab8e2b288f542d956@axis.com \
    --to=peter.kjellerstedt@axis.com \
    --cc=Ross.Burton@arm.com \
    --cc=bruce.ashfield@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox