From: "Peter Kjellerstedt" <peter.kjellerstedt@axis.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>,
Michael Opdenacker <michael.opdenacker@bootlin.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] meta: stop using "virtual/" in RPROVIDES and RDEPENDS
Date: Wed, 1 Sep 2021 14:46:48 +0000 [thread overview]
Message-ID: <f6c7916efaf24021815101c3b0086782@axis.com> (raw)
In-Reply-To: <CADkTA4NCnTW5Zx=UJ9Lk0szNdJqENZyZL=pNJVmMXanBHEYr6A@mail.gmail.com>
> -----Original Message-----
> From: openembedded-core@lists.openembedded.org <openembedded-
> core@lists.openembedded.org> On Behalf Of Bruce Ashfield
> Sent: den 1 september 2021 15:24
> To: Michael Opdenacker <michael.opdenacker@bootlin.com>
> Cc: Patches and discussions about the oe-core layer <openembedded-
> core@lists.openembedded.org>
> Subject: Re: [OE-core] [PATCH] meta: stop using "virtual/" in RPROVIDES
> and RDEPENDS
>
> On Wed, Sep 1, 2021 at 5:20 AM Michael Opdenacker
> <michael.opdenacker@bootlin.com> wrote:
> >
> > Fixes [YOCTO #14538]
> >
> > Recipes shouldn't use the "virtual/" string in RPROVIDES and RDEPENDS.
> >
> > That's confusing because "virtual/" has no special meaning in
> > RPROVIDES and RDEPENDS (unlike in PROVIDES and DEPENDS).
> >
> > Instead, using "virtual-" instead of "virtual/"
> > as already done in the glibc recipe.
>
> We have quite a few cases in meta-virtualization, where the same
> unclear syntax is used.
>
> I can take care of updating it, if you aren't looking at it already.
>
> Bruce
Can anyone enlighten me to what benefit changing "virtual/" to
"virtual-" for runtime dependencies gives? AFAIU, this makes no
technical difference and everything will still work exactly as
before, but with a different provided name.
If you then have virtual/foo for build dependencies and virtual-foo
for the corresponding runtime dependencies, then I only see increased
confusion with a change like this.
And yes, I know about the problems with virtual runtime dependencies,
but in my experience, as long as you do not try to create a global
package repository with packages from multiple builds, but only use
the packages created by bitbake to generate an image, they work as
expected.
//Peter
next prev parent reply other threads:[~2021-09-01 14:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-01 9:20 [PATCH] meta: stop using "virtual/" in RPROVIDES and RDEPENDS Michael Opdenacker
2021-09-01 13:23 ` [OE-core] " Bruce Ashfield
2021-09-01 14:46 ` Peter Kjellerstedt [this message]
2021-09-01 14:52 ` Bruce Ashfield
2021-09-01 15:06 ` Richard Purdie
2021-09-01 17:10 ` Michael Opdenacker
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=f6c7916efaf24021815101c3b0086782@axis.com \
--to=peter.kjellerstedt@axis.com \
--cc=bruce.ashfield@gmail.com \
--cc=michael.opdenacker@bootlin.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