From: Phil Blundell <philb@gnu.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: AUTOREV and SRCPV
Date: Thu, 03 Jun 2010 17:35:29 +0100 [thread overview]
Message-ID: <1275582929.15559.65.camel@mill.internal.reciva.com> (raw)
In-Reply-To: <1275555319.4657.42.camel@lenovo.internal.reciva.com>
On Thu, 2010-06-03 at 09:55 +0100, Phil Blundell wrote:
> On Thu, 2010-06-03 at 10:46 +0200, Martin Jansa wrote:
> > So will bitbake build again the same recipe (because I've built from the
> > same one before) with lower PV, just because it _still_ has the highest
> > DEFAULT_PREFERENCE and it's desired version (but still lower PV because
> > of hash, then before)?.
>
> Yes, I think so. PV, and hence P, will be different and that's about
> all that matters to bitbake. The fact that PF is the same should be
> irrelevant; I don't think any of its persistent state is keyed on that.
I did a quick test on this and it does indeed seem to work as you would
expect. So that seems like the easiest way of solving the problem at
hand.
p.
next prev parent reply other threads:[~2010-06-03 16:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-02 21:51 AUTOREV and SRCPV pieterg
2010-06-03 4:35 ` Martin Jansa
2010-06-03 7:15 ` pieterg
2010-06-03 7:37 ` Martin Jansa
2010-06-03 8:02 ` pieterg
2010-06-03 8:27 ` Martin Jansa
2010-06-03 8:44 ` pieterg
2010-06-03 9:22 ` pieterg
2010-06-03 8:13 ` Phil Blundell
2010-06-03 8:30 ` Martin Jansa
2010-06-03 8:37 ` Phil Blundell
2010-06-03 8:46 ` Martin Jansa
2010-06-03 8:55 ` Phil Blundell
2010-06-03 16:35 ` Phil Blundell [this message]
2010-06-04 8:24 ` pieterg
2010-06-04 8:30 ` Phil Blundell
2010-06-04 8:44 ` pieterg
2010-06-04 11:03 ` Phil Blundell
2010-06-05 10:36 ` pieterg
2010-06-06 21:00 ` Phil Blundell
2010-06-07 0:13 ` Khem Raj
2010-06-08 10:09 ` Phil Blundell
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=1275582929.15559.65.camel@mill.internal.reciva.com \
--to=philb@gnu.org \
--cc=openembedded-devel@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