From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@openembedded.org
Subject: Re: SCM fetched recipes without a SRCREV - e.g. libgee-native
Date: Thu, 22 Oct 2009 09:44:54 +0100 [thread overview]
Message-ID: <1256201094.23211.64.camel@dax.rpnet.com> (raw)
In-Reply-To: <20091022005956.GA11194@denix.org>
On Wed, 2009-10-21 at 20:59 -0400, Denys Dmytriyenko wrote:
> On Wed, Oct 21, 2009 at 07:57:40PM +0100, Richard Purdie wrote:
> > On Wed, 2009-10-21 at 13:42 +0200, Michael 'Mickey' Lauer wrote:
> > > Am Mittwoch, den 21.10.2009, 13:21 +0200 schrieb Koen Kooi:
> > > > If we continue down the sane-srcrevs.inc route we should consider moving
> > > > PV_pn into there as well. Having SRCREV and PN in 2 different places
> > > > only adds confusion and leads to misversions.
> > >
> > > Correct.
> > >
> > > > Speaking of misversioning, I should really go through all scm fetched
> > > > packages I use and verify PV is correct for those.
> > >
> > > Agreed, will have to do the same here.
> >
> > Can I also suggest we start using SRCPV in PV, not SRCREV? This removed
> > the need to play a lot of games with PV...
> >
> > (Poky has switched to this now)
>
> AFAIK, it's not merged in OE yet. I would definitely like to see it in OE.
> Last time we discussed it, the agreement was to introduce SRCPV in
> bitbake.conf first and then gradually switch existing recipes over from
> SRCREV, instead of mass-updating all of them at once...
Either way is fine but this looks like a good time to think about it if
we're already assessing the variables!
Cheers,
Richard
next prev parent reply other threads:[~2009-10-22 8:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-21 10:47 SCM fetched recipes without a SRCREV - e.g. libgee-native Koen Kooi
2009-10-21 11:03 ` Holger Hans Peter Freyther
2009-10-21 11:10 ` Michael 'Mickey' Lauer
2009-10-21 11:21 ` Koen Kooi
2009-10-21 11:42 ` Michael 'Mickey' Lauer
2009-10-21 18:57 ` Richard Purdie
2009-10-22 0:59 ` Denys Dmytriyenko
2009-10-22 8:44 ` Richard Purdie [this message]
2009-10-21 11:15 ` Robert P. J. Day
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=1256201094.23211.64.camel@dax.rpnet.com \
--to=rpurdie@rpsys.net \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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