[RFC] SRCREV in PV for git packages

Holger Freyther zecke at openmoko.org
Tue May 13 01:46:40 CEST 2008

if you use SRCREV inside the PV and have a SRCREV_pn-foo in a config file, you 
will end with packages that might or might not be upgradable. Only for SRCREV 
= AUTOREV as sortable revision is generated.

At Openmoko I'm currently trying the following fix to this issue and would 
like to get some feedback to it. Once I push I will send you my changes as 

+SRCPV = "${bb.fetch.get_srcrev(d)}"

change SRCREV in the PV to SRCPV in all packages.

Q: What does it do?
A: It makes sure that Bitbake can give it a sortable revision

Q: Why does it work?
A: The Bitbake fetchers use an internal function to determine if AUTOREV is 
used or a specific branch/rev was requested. The internal function works with 
SRCREV which is still set (either by AUTOREV or a revision). The second call 
to get_srcrev will actually return the revision as used.

comments? is that just exploiting something internal of Bitbake? Is that bad?


More information about the distro-devel mailing list