Re: SRCPV migration

[Koen Kooi <k.kooi@student.utwente.nl>]

On 15-11-09 17:36, Martin Jansa wrote:
> As I sent earlier as reply to [PATCH] bitbake.conf: SRCPV always upgradeable
> paths for git recipes.
>
> First few changes are already in martin_jansa/srcpv branch. All changes to svn.bb
> recipes seems safe, so I would like to push them really soon. For git.bb changes
> I need your advise/ack so please reply.
>
> Original e-mail:
>
> 1) svn recipes with +svnr{SRCREV} could be just replaced with
> +svnr{SRCPV} as the output should be the same
>
> 2) svn recipes with -r{SRCREV}, -svn{SRCREV}, -svnr{SRCREV}, +r{SRCREV},
> +svn{SRCREV} unified to +svnr{SRCPV}? I'm not sure if '+' will be sorted
> higher version wise, so do we need to bump PE?
>
> 3) git recipes with -git{SRCREV}, -gitr{SRCREV}, +git{SRCREV} unified to
> +gitr{SRCPV} with PE bump?

If something needs a PE bump, make sure you do it properly and bump PE 
on the non scm fetched entries as well. For the kernel I wouldn't bump 
PE, since too many machines can use different kernel recipes.

And can someone tell me how SRCPV works when you have multiple 
buildmachines across the world, how does one keep SRCPV in sync between 
all those machines?

How does SRCPV work when you have recipes for 1.2+gitrfoo, 1.3+gitrbar, etc?

IOW: will it create more work for me (like the proposed checksums 
changes) instead of making things easier?

regards,

Koen