On Thursday, September 25, 2014, Burton, Ross wrote:
> On 25 September 2014 00:43, Martin Jansa > wrote:
> > Include SRCPV in your PV, otherwise do_fetch signature won't be changed
> > when you change just SRCREV so it won't update it for you.
> >
> > You can also add it explicitly
> > do_fetch[
On 25 September 2014 00:43, Martin Jansa wrote:
> Include SRCPV in your PV, otherwise do_fetch signature won't be changed
> when you change just SRCREV so it won't update it for you.
>
> You can also add it explicitly
> do_fetch[vardeps] += "SRCREV"
As SRCREV does change the fetcher behaviour, sh
On Wed, Sep 24, 2014 at 03:04:46PM -0700, Leo Schwab wrote:
> I suspect this is a common issue, but my Google-fu has gotten me no closer
> to understanding what I might be doing wrong, so here goes:
>
> We have written recipes for various goodies -- both .bb and .bbappend forms
> -- where SRC_URI
On 24 September 2014 23:04, Leo Schwab wrote:
> We have written recipes for various goodies -- both .bb and .bbappend forms
> -- where SRC_URI points to a Git repository, and SRCREV names a commit ID
> (not a tag or a branch name). When we update the SRCREV to something newer,
> 'bitbake' goes th
I suspect this is a common issue, but my Google-fu has gotten me no closer
to understanding what I might be doing wrong, so here goes:
We have written recipes for various goodies -- both .bb and .bbappend forms
-- where SRC_URI points to a Git repository, and SRCREV names a commit ID
(not a tag or