From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Cliff Brake <cliff.brake@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: How to use externalsrc with git workspace
Date: Tue, 29 Mar 2016 13:28:42 +0100 [thread overview]
Message-ID: <1459254522.21672.24.camel@linuxfoundation.org> (raw)
In-Reply-To: <56FA743B.5030200@gmail.com>
On Tue, 2016-03-29 at 08:25 -0400, Cliff Brake wrote:
> On 03/28/2016 06:28 PM, Richard Purdie wrote:
> > > I tried nobranch=1;rev=HEAD, but then that conflicts with
> > > ${AUTOREV}.
> > Did you just try nobranch=1 and leave rev to get set from SRCREV?
>
> That will parse, but it puts the wrong git rev in the PV:
>
> The following package gets built:
>
> blkqcl-app-tune_1.4+gitr1+a97fcb58e6-r1.0_cortexa9hf-vfp-neon.ipk
>
> But, the actual version of the source that gets built is
> 0edb656fc9a1a77d75eaa49a17586deb4c986bb1.
>
> a97... is the version of the branch (default is master) in the
> workspace.
>
> So this would work if we did not care what gitv got put in the PV.
> There is
> also the issue of bitbake not rebuilding the source if you change the
> git
> version of the workspace, but the branch happens to not change.
At least from my perspective, this is what *should* work and the fact
it doesn't is a bug somewhere. Adding extra things to the fetcher would
likely just workaround it. Filing a bug report for it would be the
likely next step.
Cheers,
Richard
next prev parent reply other threads:[~2016-03-29 12:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-25 20:18 How to use externalsrc with git workspace Cliff Brake
2016-03-25 21:07 ` Cliff Brake
2016-03-26 7:41 ` Richard Purdie
2016-03-28 19:58 ` Cliff Brake
2016-03-28 22:28 ` Richard Purdie
2016-03-29 12:25 ` Cliff Brake
2016-03-29 12:28 ` Richard Purdie [this message]
2016-03-29 13:50 ` Cliff Brake
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=1459254522.21672.24.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=cliff.brake@gmail.com \
--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