[oe] Setting `PV` in recipes using SCM repositories (was: [PATCH v3] enna: Move to own recipe folder and update to new Enna hg repository.)

[Paul Menzel]

Am Freitag, den 02.04.2010, 23:18 +0200 schrieb Martin Jansa:
> On Fri, Apr 02, 2010 at 11:28:10AM -0700, Khem Raj wrote:
> > On Fri, Apr 2, 2010 at 8:59 AM, Paul Menzel
> > <paulepanter at users.sourceforge.net> wrote:
> > > 1. Create `enna.inc`.
> > > 2. Use `INC_PR`.
> > > 3. Move to new repository location.
> > > 4. Use `NOTQUITESRCREV` since `SRCREV` seems to get set to the one from the EFL recipes.
> 
> You can use SRCREV again after
> http://git.openembedded.org/cgit.cgi/openembedded/commit/?id=82b394467d9142edf2721176244c3a7eb26ba69a

I guess I have to resend a v4.

> And maybe you want rev shown in PV or PR
> PV = "0.4.0+hg${SRCPV}" or 
> PR_append = "+hg${SRCPV}"
> is quire common and should work for hg too (haven't checked)

Unfortunately I could not find any information about `SRCPV` in the
BitBake or OE manual. What is the difference to `SRCREV`?

Anyway, the problem I have with appending the `SRCREV` to `PV` is, that
if you change the revision `bitbake -c clean recipe.bb` will not work
and the old files stay in the build tree. Is that true with `SRCPV`
also?

Could the TSC make a suggestion on how to set `PV` in recipes using SCM
repositories.


Thanks,

Paul
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
URL: <http://lists.openembedded.org/pipermail/openembedded-devel/attachments/20100403/dfbfe8c2/attachment-0002.sig>