From: Martin Jansa <martin.jansa@gmail.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Chris Larson <clarson@kergoth.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 22:03:06 +0100 [thread overview]
Message-ID: <20130130210306.GA2102@jama.dyndns-home.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1301301535390.3782@oneiric>
[-- Attachment #1: Type: text/plain, Size: 1227 bytes --]
On Wed, Jan 30, 2013 at 03:37:45PM -0500, Robert P. J. Day wrote:
> 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
There is also rebaseable parameter for git:// fetcher to generate
versioned snapshot from repository and reuse that in future build
(like fetcher1 did, see https://bugzilla.yoctoproject.org/show_bug.cgi?id=1511).
That should be used in that SRC_URI.
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
prev parent reply other threads:[~2013-01-30 21:19 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
2013-01-30 20:44 ` Chris Larson
2013-01-30 21:31 ` Robert P. J. Day
2013-01-30 21:03 ` Martin Jansa [this message]
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=20130130210306.GA2102@jama.dyndns-home.com \
--to=martin.jansa@gmail.com \
--cc=clarson@kergoth.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=rpjday@crashcourse.ca \
/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