Re: SRCPV migration - How SRCPV works!

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

On Mon, Nov 23, 2009 at 04:00:26PM +0100, Koen Kooi wrote:
> On 23-11-09 15:29, Richard Purdie wrote:
> >On Mon, 2009-11-23 at 14:31 +0100, Koen Kooi wrote:
> >>On 23-11-09 13:15, Richard Purdie wrote:
> >>
> >>>As I understand it you'll lock locking down the local build revisions
> >>>with Angstrom anyway?
> >>
> >>Dunno about that, ideally the SRCPV merge should have no impact at all
> >>on existing distros, but it looks like everyone will be forced to lock
> >>revisions/counts down.
> >
> >How is locking the counts down using LOCALCOUNT any different to the
> >current situation?
> 
> In the current situation you lock down SRCREV and change PV,PR
> accordingly. In the new world you lock down SRCREV, increase
> localcount (per recipe or globally) and change PV,PR accordingly.

Why do you need to change PV,PR if you bump LOCALCOUNT?

> I just went from a 2 step error prone situation to a 3 step error
> prone situation. And I need to track an *extra* variable as well
> now.

I see only 1 step in one place (SRCREV+LOCALCOUNT in sane-srcrevs or
recipe). And as long as its in the same file, it can be a bit less
error-prone then change of SRCREV in sane-srcrevs and PV/PR bump in
recipe.

> regards,

regards,

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