From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] superfluous usage of "INC_PR" in oe-core?
Date: Tue, 5 May 2020 08:19:18 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.21.2005050817170.11221@localhost.localdomain> (raw)
In-Reply-To: <0f91729190f8b3c6ad5f07eea053635450a2197b.camel@linuxfoundation.org>
On Tue, 5 May 2020, Richard Purdie wrote:
> On Sun, 2020-05-03 at 13:07 -0400, Robert P. J. Day wrote:
> > given my understanding of the rationale for INC_PR, it would seem
> > as
> > if at least *some* of these assignments are superfluous:
> >
> > recipes-connectivity/connman/connman.inc:INC_PR = "r20"
> > recipes-graphics/xorg-driver/xorg-driver-common.inc:INC_PR = "r21"
> > recipes-graphics/xorg-xserver/xserver-xorg.inc:INC_PR = "r8"
> > recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
> > recipes-graphics/xorg-font/xorg-font-common.inc:INC_PR = "r2"
> > recipes-graphics/xorg-font/encodings_1.0.5.bb:PR = "${INC_PR}.1"
> > recipes-graphics/xorg-app/xorg-app-common.inc:INC_PR = "r8"
> > recipes-kernel/linux/linux-yocto.inc:INC_PR = "r4"
>
> This is a bit of a historical relic, I've sent a patch to clean it up.
just to be clear, while there's not much value to INC_PR anymore,
it's still officially supported, yes? (there are a small number of
occurrences in meta-openembedded as well.)
rday
next prev parent reply other threads:[~2020-05-05 12:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-03 17:07 superfluous usage of "INC_PR" in oe-core? Robert P. J. Day
2020-05-05 9:58 ` [OE-core] " Richard Purdie
2020-05-05 12:19 ` Robert P. J. Day [this message]
2020-05-05 12:40 ` 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=alpine.LFD.2.21.2005050817170.11221@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--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