From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Evade Flow <evadeflow@gmail.com>,
Christopher Larson <clarson@kergoth.com>
Cc: Poky <poky@yoctoproject.org>
Subject: Re: When SRCREV is set to AUTOREV, what triggers (re-)fetching?
Date: Fri, 02 Sep 2016 15:35:06 +0100 [thread overview]
Message-ID: <1472826906.29583.167.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAMAb8ZOEiy_u4MtGF7xXMR9w8AYFwCPSTmbOZ70mBj7_e1gbSQ@mail.gmail.com>
On Fri, 2016-09-02 at 10:08 -0400, Evade Flow wrote:
> > Add ${SRCPV} to your PV (see various recipes in oe-core for
> examples), then it’ll know to re-run the tasks when srcrev changes.
>
> Thanks for confirming that this is 'supposed' to work, that's great
> news! Actually, I've already included SRCPV in PV. Here's my recipe,
> shorn of comments and an uninteresting do_install_append() function:
You don't have BB_SRCREV_POLICY set to cache anywhere do you? It
defaults to clear which is what you want...
Does "rm tmp/cache -r" 'fix' make it see new revisions? Knowing that
would at least help track down the kind of problem you're seeing.
What does the full PV look like after expansion? Does it contain an
older truncated SRCREV ?
Cheers,
Richard
next prev parent reply other threads:[~2016-09-02 14:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-01 22:14 When SRCREV is set to AUTOREV, what triggers (re-)fetching? Evade Flow
2016-09-01 22:16 ` Christopher Larson
2016-09-02 14:08 ` Evade Flow
2016-09-02 14:35 ` Richard Purdie [this message]
2016-09-02 18:16 ` Jianxun Zhang
2016-09-02 18:46 ` Evade Flow
2016-09-02 18:20 ` Evade Flow
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=1472826906.29583.167.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=clarson@kergoth.com \
--cc=evadeflow@gmail.com \
--cc=poky@yoctoproject.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.