public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
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:37:45 -0500 (EST)	[thread overview]
Message-ID: <alpine.DEB.2.02.1301301535390.3782@oneiric> (raw)
In-Reply-To: <CABcZANmn_EP_qGszxtsEymkMFe4iHDsWvXGc2wtc0pSieMTjSQ@mail.gmail.com>

On Wed, 30 Jan 2013, Chris Larson 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.

  i'm not in the least embarrassed to admit i didn't even know that
variable existed.  and, yes, that pretty much solves the problem.

  i'm still creeped out by that comment of using the tag name to deal
with rebasing a public commit, though.  :-P

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================



  parent reply	other threads:[~2013-01-30 20:53 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
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 [this message]
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=alpine.DEB.2.02.1301301535390.3782@oneiric \
    --to=rpjday@crashcourse.ca \
    --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