[oe] buildindex is always 0, using BB_GIT_CLONE_FOR_SRCREV = "1"

[Radoslav Kolev]

On Mon, May 2, 2011 at 2:03 PM, Martin Jansa <martin.jansa at gmail.com> wrote:
> On Mon, May 02, 2011 at 12:51:22PM +0200, Eric Bénard wrote:
>> Hi Radoslav,
>>
>> On 02/05/2011 12:18, Radoslav Kolev wrote:
>> > In the recipe I have
>> >
>> > SRCREV = "${AUTOREV}"
>> > PV = "0.4+gitr-${SRCPV}"
>> >
>> replace SRCPV with SRVREV in PV and you will the the rev instead of O.
>
> and no upgradeable path at all when changing SRCREV or even using
> AUTOREV like in example.

I tried using SRCREV instead of SRCPV in PV as Eric suggested, just to
see what happens. And at least at first glance in my concrete case
there was no difference. The package generated had the counter
incremented same as with  SRCPV -
169+33203fbe6c3ab029fba3e31a12e36ef8b56bb61fl. Is there something I'm
missing that will actually cause this to not work.

I've read the "SRCPV migration" thread from around two years ago, and
what other relevant information I could find in the mailing list
archives. I can't claim to have really grasped all of it though. What
I got out of this reading was that SRCPV var was intended to be used
as part of PV and so I did to follow the best practice, but I'd be
curious to know what exactly is the difference in this case.

> And BTW there usually isn't '-' between gitr and ${SRCPV} see recipes in
> tree.

Thanks! This is just for an internal project, but I'll change it
anyway to be consistent with the accepted style.

Radoslav Kolev