Re: [RFC] Make some big but only formal change before next stable - SRCPV

[Martin Jansa <martin.jansa@gmail.com>]

On Tue, Mar 09, 2010 at 10:36:28AM +0000, Phil Blundell wrote:
> On Tue, 2010-03-09 at 08:53 +0100, Martin Jansa wrote:
> > My SRCPV migration branch is quickly rotting.. but I'm willing to
> > check/do it again, because resolving conflicts with every small change
> > in git recipe takes me more time than merging SRCPV to oe.dev would
> > take.
> 
> At the risk of sounding like a terrible dimwit, I am still not entirely
> clear on why you can't just do something like

Feeling the same here now..

> PKGV = "0.0+git${@bb.fetch.get_srcrev(d)}.${PV}"

How this should work?

is PV at the end typo from PR or do you really mean that srcrev has higher
priority than PV?

> which seems like it would make this whole problem go away without
> needing any further changes to bitbake.

All changes are already there. What's new in master is optional support
for forcing that incrementing part to same value across builders, without
local cache synchronization.

And also caching for revs returned when using BB_GIT_CLONE_FOR_SRCREV,
which can improve performance instead of running "git rev-list | wc -l"
with every get_srcrev(d).

Regards,

-- 
uin:136542059                jid:Martin.Jansa@gmail.com
Jansa Martin                 sip:jamasip@voip.wengo.fr 
JaMa