what's the easiest way to download *all* recipe-referenced tarballs?

what's the easiest way to download *all* recipe-referenced tarballs?

[Robert P. J. Day]

  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.

  is there a better way?  i just want a stash of tarballs ready to go
so we don't waste a lot of time downloading.

rday

-- 

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

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

Re: what's the easiest way to download *all* recipe-referenced tarballs?

[Saul Wold]

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, it should get everthing, unless there is a 
MACHINE-specific variable in SRC_URI, which I don't think we have.

Sau!

>    is there a better way?  i just want a stash of tarballs ready to go
> so we don't waste a lot of time downloading.
>
> rday
>

Re: what's the easiest way to download *all* recipe-referenced tarballs?

[Robert P. J. Day]

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?

rday

-- 

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

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

Re: what's the easiest way to download *all* recipe-referenced tarballs?

[Saul Wold]

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
>