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: Mon, 05 Sep 2011 20:31:17 +0100 [thread overview]
Message-ID: <1315251077.1243.16.camel@ted> (raw)
In-Reply-To: <CAP9ODKpdUMKw0RUHgzy5LnEupR9+wOuan7xiekefGitHSROBbw@mail.gmail.com>
On Mon, 2011-08-29 at 14:24 -0300, Otavio Salvador wrote:
> On Sun, Aug 28, 2011 at 04:41, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > 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 \
> > "
>
> I did it locally and it ...:
>
> - does the clones in DL_DIR file
> - gets the right SRCREV for both
> - gets the right SRCPV
>
> However on unpack it fails; it always use S as '${WORKDIR}/git' even
> if I change it in the recipe.
>
> Something seems broken on bitbake support for it.
>
> Clues?
Just to follow up for the benefit of the mailing list, we were missing a
patch Holger submitted a while back for this problem which has now
merged into bitbake master. You can now tell the fetcher to use
something other than "git" as the checkout directory.
Cheers,
Richard
next prev parent reply other threads:[~2011-09-05 19:36 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
2011-08-29 17:24 ` Otavio Salvador
2011-09-05 19:31 ` Richard Purdie [this message]
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=1315251077.1243.16.camel@ted \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.