From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [206.46.173.19] (helo=vms173019pub.verizon.net) by linuxtogo.org with esmtp (Exim 4.69) (envelope-from ) id 1Me3no-0002KF-C1 for openembedded-devel@lists.openembedded.org; Thu, 20 Aug 2009 11:19:27 +0200 Received: from gandalf.denix.org ([71.255.235.240]) by vms173019.mailsrvcs.net (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPA id <0KOO001QS3QOBCD1@vms173019.mailsrvcs.net> for openembedded-devel@lists.openembedded.org; Thu, 20 Aug 2009 04:01:37 -0500 (CDT) Received: by gandalf.denix.org (Postfix, from userid 1000) id 54F1214AF5F; Thu, 20 Aug 2009 05:01:36 -0400 (EDT) Date: Thu, 20 Aug 2009 05:01:36 -0400 From: Denys Dmytriyenko To: openembedded-devel@lists.openembedded.org Message-id: <20090820090136.GD459@denix.org> References: <20090820032802.GA32010@denix.org> <200908200752.58210.holger+oe@freyther.de> <20090820071052.GA459@denix.org> MIME-version: 1.0 In-reply-to: User-Agent: Mutt/1.5.16 (2007-06-09) Subject: Re: Use AUTOREV and have revision/commit number in package name? 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, 20 Aug 2009 09:19:41 -0000 Content-type: text/plain; charset=us-ascii Content-disposition: inline On Thu, Aug 20, 2009 at 10:34:58AM +0200, Koen Kooi wrote: > On 20-08-09 09:10, Denys Dmytriyenko wrote: >> On Thu, Aug 20, 2009 at 07:52:58AM +0200, Holger Hans Peter Freyther >> wrote: >>> On Thursday 20 August 2009 05:28:02 Denys Dmytriyenko wrote: >>>> Now, when SRCREV = "${AUTOREV}", AUTOREV gets resolved into a Python >>>> function, which does the magic of fetching the latest snapshot from a >>>> repository. But now if PV contains references to SRCREV, it breaks >>>> (undesrandably), since SRCREV gets resolved in do_fetch and PV needs to >>>> be >>>> resolved early on. >>>> >>>> Are there any standard ways to work around this limitation? >>> >>> Check the mailinglist archives... Openmoko has deployed a solution that >>> has >>> fixed that about 1 1/2 years ago. >>> >>> Short answer: >>> - Do not put SRCREV into PV, e.g. create a new var called SRCPV >>> - Populate SRCPV with something based on the SRCREV.. >> >> Ah, thanks! I was able to find your RFC message from last year on the >> Openmoko >> mailing list: >> http://markmail.org/message/v3s32gmxxqcaxpph >> >> I'll give it a try. Thanks. >> >> To be clear - it's not used in OE. While there is a single >> python-phoneutils >> recipe, which references SRCPV, it is not being set anywhere, >> apparently... > > Take a look at > http://cgit.openembedded.org/cgit.cgi/openembedded/log/?h=xora/angstrom-srcpv > :) Thanks! More specifically: http://cgit.openembedded.org/cgit.cgi/openembedded/commit/?h=xora/angstrom-srcpv&id=453a13c7a68087895f4048410aba1a519ec99897 Any ETA for the merge back to .dev? :) -- Denys