All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: AUTOREV and SRCPV
Date: Thu, 3 Jun 2010 10:46:31 +0200	[thread overview]
Message-ID: <20100603084631.GN16035@jama> (raw)
In-Reply-To: <1275554237.4657.40.camel@lenovo.internal.reciva.com>

On Thu, Jun 03, 2010 at 09:37:17AM +0100, Phil Blundell wrote:
> On Thu, 2010-06-03 at 10:30 +0200, Martin Jansa wrote:
> > On Thu, Jun 03, 2010 at 09:13:37AM +0100, Phil Blundell wrote:
> > > but I think that's already fixable
> > > with strategic use of PREFERRED_VERSION and/or DEFAULT_PREFERENCE.
> > 
> > How? Can you explain in more detail?
> 
> If you arrange for the autorev'd recipe to be, say,
> DEFAULT_PREFERENCE=1, then I think bitbake will treat it as the desired
> version to build even if SRCREV - and hence PV - would sort lower than
> some other version (irrespective of whether that other version has
> already been built or not).  Then you just need to engineer PKGV to be
> suitably monotonic in order to get the right things to happen inside
> deploy/ and on the target system.

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)?.

Maybe I had not enough coffee today, but I still don't understand it,
sorry, maybe someone else can comment?

Regards,

-- 
uin:136542059                jid:Martin.Jansa@gmail.com
Jansa Martin                 sip:jamasip@voip.wengo.fr 
JaMa                         



  reply	other threads:[~2010-06-03  8:50 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 [this message]
2010-06-03  8:55               ` Phil Blundell
2010-06-03 16:35                 ` Phil Blundell
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=20100603084631.GN16035@jama \
    --to=martin.jansa@gmail.com \
    --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 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.