From: Harvey Chapman <hchapman-oecore@3gfp.com>
To: Chris Larson <clarson@kergoth.com>
Cc: Martin Jansa <martin.jansa@gmail.com>,
OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: BB_NO_NETWORK = "1" causes fetch to fail for unnecessary u-boot parsing
Date: Wed, 30 Jan 2013 15:49:10 -0500 [thread overview]
Message-ID: <3C2BEFD8-C67F-4356-9518-5E91D1B975D4@3gfp.com> (raw)
In-Reply-To: <CABcZAN=urVqvHFj_EkRXfkDUpbNb51Lr7taPWiPYXqqU__Cigw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 800 bytes --]
On Jan 30, 2013, at 3:34 PM, Chris Larson <clarson@kergoth.com> wrote:
> On Wed, Jan 30, 2013 at 1:34 PM, Chris Larson <clarson@kergoth.com> wrote:
>
> It's worth bringing up the SRCREV_POLICY variable, which lets you control how bitbake handles caching of srcrevs. By default, it figures it needs to get the mapping every time (value == clear, or unset), which can make sense in certain cases. But you can tell it to go ahead and use the values it has cached from a previous run, as well (value == cache). This can be useful if you know you're moving into an offline state and want to prepare for it above and beyond the -c fetchall.
>
> Erm, s/SRCREV_POLICY/BB_SRCREV_POLICY/
So, should BB_NO_NETWORK=1 automatically set BB_SRCREV_POLICY=cache because the former implies the latter?
[-- Attachment #2: Type: text/html, Size: 1609 bytes --]
next prev parent reply other threads:[~2013-01-30 21:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 9:08 BB_NO_NETWORK = "1" causes fetch to fail for unnecessary u-boot parsing Robert P. J. Day
2013-01-29 9:44 ` Martin Jansa
2013-01-29 9:54 ` Robert P. J. Day
2013-01-29 11:24 ` Martin Jansa
2013-01-30 20:27 ` Robert P. J. Day
2013-01-30 20:34 ` Chris Larson
2013-01-30 20:34 ` Chris Larson
2013-01-30 20:49 ` Harvey Chapman [this message]
2013-01-30 20:53 ` Robert P. J. Day
2013-01-30 20:57 ` Chris Larson
2013-01-30 20:37 ` Robert P. J. Day
2013-01-30 20:44 ` Chris Larson
2013-01-30 21:31 ` Robert P. J. Day
2013-01-30 21:03 ` Martin Jansa
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=3C2BEFD8-C67F-4356-9518-5E91D1B975D4@3gfp.com \
--to=hchapman-oecore@3gfp.com \
--cc=clarson@kergoth.com \
--cc=martin.jansa@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