Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Marco Cavallini <koansoftware@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Setting `PV` in recipes using SCM repositories
Date: Sun, 04 Apr 2010 10:43:42 +0200	[thread overview]
Message-ID: <4BB8513E.40705@gmail.com> (raw)
In-Reply-To: <1270249002.3714.29.camel@mattotaupa>

Paul Menzel ha scritto, Il 03/04/2010 00:56:
> 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@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
> 
> 
> ------------------------------------------------------------------------

I'll work on this next week

Happy Easter :-)


Cordiali Saluti / Kindest Regards / mit freundlichen Grüssen
--
Marco Cavallini | KOAN sas | Bergamo - Italia
 embedded and real-time software engineering
Phone:+39-035-255.235 - Fax:+39-178-22.39.748
      http://www.KoanSoftware.com



  reply	other threads:[~2010-04-04  8:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-28 17:18 [PATCH] enna: Move to own recipe folder and update to enna hg Paul Menzel
2010-03-30 13:20 ` [PATCH v2] " Paul Menzel
2010-04-02 15:59   ` [PATCH v3] enna: Move to own recipe folder and update to new Enna hg repository Paul Menzel
2010-04-02 18:28     ` Khem Raj
2010-04-02 19:44       ` Paul Menzel
2010-04-03 11:20         ` autopoint || touch config.rpath (was: [PATCH v3] enna: Move to own recipe folder and update to new Enna hg repository.) Paul Menzel
2010-04-03 13:51           ` Jens Seidel
2010-04-03 14:43             ` autopoint || touch config.rpath Paul Menzel
2010-04-07 15:44               ` Jens Seidel
2010-04-08  8:01                 ` Richard Purdie
2010-04-02 21:18       ` [PATCH v3] enna: Move to own recipe folder and update to new Enna hg repository Martin Jansa
2010-04-02 22:56         ` 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
2010-04-04  8:43           ` Marco Cavallini [this message]
2010-04-03 11:03         ` [PATCH v4] enna: Move to own recipe folder and update to new Enna hg repository Paul Menzel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4BB8513E.40705@gmail.com \
    --to=koansoftware@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox