From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.reciva.com ([109.169.29.93] helo=crown.reciva.com) by linuxtogo.org with esmtp (Exim 4.69) (envelope-from ) id 1OK5zR-0007Uf-Mf for openembedded-devel@lists.openembedded.org; Thu, 03 Jun 2010 10:41:29 +0200 Received: from jost.swaffham-prior.co.uk ([217.154.114.20] helo=[192.168.114.10]) by crown.reciva.com with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1OK5vM-0007Pa-3R for openembedded-devel@lists.openembedded.org; Thu, 03 Jun 2010 09:37:12 +0100 From: Phil Blundell To: openembedded-devel@lists.openembedded.org In-Reply-To: <20100603083011.GM16035@jama> References: <201006022351.38129.pieterg@gmx.com> <20100603043505.GJ16035@jama> <201006030915.57362.pieterg@gmx.com> <20100603073717.GK16035@jama> <1275552817.4657.32.camel@lenovo.internal.reciva.com> <20100603083011.GM16035@jama> Date: Thu, 03 Jun 2010 09:37:17 +0100 Message-ID: <1275554237.4657.40.camel@lenovo.internal.reciva.com> Mime-Version: 1.0 X-Mailer: Evolution 2.28.1 X-SA-Exim-Connect-IP: 109.169.29.93 X-SA-Exim-Mail-From: philb@gnu.org X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on discovery X-Spam-Level: X-Spam-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00,SPF_SOFTFAIL autolearn=no version=3.2.5 X-SA-Exim-Version: 4.2.1 (built Wed, 25 Jun 2008 17:20:07 +0000) X-SA-Exim-Scanned: Yes (on linuxtogo.org) Subject: Re: AUTOREV and SRCPV X-BeenThere: openembedded-devel@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: openembedded-devel@lists.openembedded.org List-Id: Using the OpenEmbedded metadata to build Distributions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jun 2010 08:41:30 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit 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. Obviously you will have a problem if PV is actually identical to some previously-built version, but the whole idea of using hashes as SCM keys is predicated on the assumption that this isn't going to happen. p.