[oe] Use AUTOREV and have revision/commit number in package name?

Graeme Gregory dp at xora.org.uk
Thu Aug 20 09:48:08 UTC 2009


Denys Dmytriyenko wrote:
> 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? :)
>
>   
Not yet, I am running out of time to actually work on it, I suspect that 
monster commit is the wrong way to do it anyway.

Probably merge bitbake.conf changes. Then merge by package-name as the 
SRCPV packages should always be versioned to be the same or an upgrade 
to the old PV.

Graeme





More information about the Openembedded-devel mailing list