Re: Use AUTOREV and have revision/commit number in package name?

[Denys Dmytriyenko <denis@denix.org>]

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:
> > All,
> >
> > I've been playing with AUTOREV for some time now and also asked this
> > question before on the IRC, but so far there seems to be no easy solution
> > to the problem in subject.
> >
> > Usually, when a package is built from an SCM repository, SRCREV is set to a
> > specific commit#/tag etc. And SRCREV is also usually referenced from PV
> > (like PV = "X.Y.Z-scmr${SRCREV}") to have the revision/commit number in the
> > package name, to easily track different builds.
> >
> > 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...

-- 
Denys