From: Ulf Magnusson <ulfalizer@gmail.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2] bitbake: bitbake-layers: Make show-recipes show PR
Date: Tue, 18 Oct 2016 00:33:38 +0200 [thread overview]
Message-ID: <CAFkk2KREJY+WDZf-Ug-xS_R1k4E1mvWZwYeBt=Zv1EpWHNSM0Q@mail.gmail.com> (raw)
In-Reply-To: <23442997.E5G5x9UaiI@peggleto-mobl.ger.corp.intel.com>
On Mon, Oct 17, 2016 at 11:42 PM, Paul Eggleton
<paul.eggleton@linux.intel.com> wrote:
> Hi Ulf,
>
> On Mon, 17 Oct 2016 20:30:27 Ulf Magnusson wrote:
>> Only PE and PV were shown, which might have been an oversight. The
>> tuples passed to version_str() contain three elements (PE, PV, and PR),
>> not two.
>
> I have to say I don't recall exactly but I think it was deliberate. We're
> talking about the recipe side here - is knowing the PR value actually useful?
> It's not like you can identify the recipe in any meaningful way by the PR
> value.
It's helpful when mapping recipes to packages at least.
Waxing philosophical, maybe PR could be viewed as a "recipe revision"
with PKGR being the "package revision", in the same sense as for
PE/PKGE and PV/PKGV. That's just an excuse I made up just now though.
I intuitively expected PR to be in there.
> Cheers,
> Paul
Cheers,
Ulf
prev parent reply other threads:[~2016-10-17 22:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 18:30 [PATCH v2] bitbake: bitbake-layers: Make show-recipes show PR Ulf Magnusson
2016-10-17 18:30 ` Ulf Magnusson
2016-10-17 21:42 ` Paul Eggleton
2016-10-17 22:33 ` Ulf Magnusson [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='CAFkk2KREJY+WDZf-Ug-xS_R1k4E1mvWZwYeBt=Zv1EpWHNSM0Q@mail.gmail.com' \
--to=ulfalizer@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
/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.