From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Use of multiple GIT repositories in SRCREV but updating PV
Date: Sun, 28 Aug 2011 08:41:10 +0100 [thread overview]
Message-ID: <1314517270.5939.268.camel@rex> (raw)
In-Reply-To: <CAP9ODKp6igGGDY2AQL+VqhYZm-GmFrKKcLg=5gRMaq5jwp+2MQ@mail.gmail.com>
On Sat, 2011-08-27 at 09:18 -0300, Otavio Salvador wrote:
> On Fri, Aug 26, 2011 at 18:40, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > On Fri, 2011-08-26 at 18:06 -0300, Otavio Salvador wrote:
> >> We have two recipes that use a common static library and every time we
> >> change something on this library we need to bump PR of those recipes.
> >> We want to avoid that specially for daily builds that will be using
> >> GIT AUTOREV support.
> >>
> >> For it to work, we need to have a way to put two SRCREV in PV and then
> >> it will be rebuit every time the library changes.
> >>
> >> Any clue how to do that?
> >
> > Set the PV as usual in the recipe:
> >
> > PV = "0.0+gitr${SRCPV}"
> >
> > and then set:
> >
> > SRCREV = "${AUTOREV}"
> >
> > ?
>
> As spoted by Chris we have multiple repositories and we want that
> either change to raise a build of the recipe.
See linux-yocto as an example. You need to name the two git uris:
SRC_URI = "\
git://git.yoctoproject.org/linux-yocto-a;protocol=git;name=machine \
git://git.yoctoproject.org/linux-yocto-b;protocol=git;name=meta \
"
set a format string to determine how the revisions should be placed in
SRCPV:
SRCREV_FORMAT = "meta_machine"
specify PV:
PV = "0.0+gitr${SRCPV}"
and then something like:
SRCREV_meta = "${AUTOREV}"
SRCREV_machine = "${AUTOREV}"
Cheers,
Richard
next prev parent reply other threads:[~2011-08-28 7:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-26 21:06 Use of multiple GIT repositories in SRCREV but updating PV Otavio Salvador
2011-08-26 21:40 ` Richard Purdie
2011-08-26 21:51 ` Chris Larson
2011-08-27 12:18 ` Otavio Salvador
2011-08-28 7:41 ` Richard Purdie [this message]
2011-08-29 17:24 ` Otavio Salvador
2011-09-05 19:31 ` Richard Purdie
2011-09-05 19:55 ` Otavio Salvador
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=1314517270.5939.268.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@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