From: Saul Wold <sgw@linux.intel.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: what's the easiest way to download *all* recipe-referenced tarballs?
Date: Tue, 03 Jul 2012 09:41:50 -0700 [thread overview]
Message-ID: <4FF320CE.8040508@linux.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1207031222040.32125@oneiric>
On 07/03/2012 09:24 AM, Robert P. J. Day wrote:
> On Tue, 3 Jul 2012, Saul Wold wrote:
>
>> On 07/03/2012 08:54 AM, Robert P. J. Day wrote:
>>>
>>> followup to once upon a time post of mine, i'm prepping to give a
>>> tutorial in OE/yocto, and it would be nice if the client could, ahead
>>> of time, set up a premirror of every conceivable tarball that is used
>>> by any recipe in oe-core.
>>>
>>> can that be done? easily? i can see configuring for a build,
>>> selecting a MACHINE, then doing "bitbake -c fetchall world", or some
>>> variation thereof. but that would be MACHINE-specific.
>>>
>> We added a "universe" target for fetching and stats gathering, but
>> it's not appropriate for building,
>
> that's fine, sounds like just what i'm after.
>
>> it should get everthing, unless there is a MACHINE-specific variable
>> in SRC_URI, which I don't think we have.
>
> so you're saying that the selection of MACHINE in local.conf
> shouldn't make any difference, right? great, i'll give it a shot. uh
> ... any idea how much will be downloaded? is there a list of the
> resulting tarballs somewhere?
>
about 4G with git trees and tarballs (yes lots of files)
Sau!
> rday
>
prev parent reply other threads:[~2012-07-03 16:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-03 15:54 what's the easiest way to download *all* recipe-referenced tarballs? Robert P. J. Day
2012-07-03 16:17 ` Saul Wold
2012-07-03 16:24 ` Robert P. J. Day
2012-07-03 16:41 ` Saul Wold [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=4FF320CE.8040508@linux.intel.com \
--to=sgw@linux.intel.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