From: Robert P. J. Day <rpjday@crashcourse.ca>
To: buildroot@busybox.net
Subject: [Buildroot] how to point at a massive local archive of S/W tarballs
Date: Mon, 20 Apr 2015 09:28:43 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1504200926590.24210@localhost> (raw)
In-Reply-To: <CANQCQpZ59t+dZZDB35+870pppUk_xuiGvgyEVKNdarc1pc19Ug@mail.gmail.com>
On Mon, 20 Apr 2015, Matthew Weber wrote:
> Robert,
>
> On Wed, Apr 15, 2015 at 3:42 PM, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
> >
> >
> > (NOTE: first of a few fairly basic questions as i play with the
> > current buildroot after being away for a bit.)
> >
> > if i'm starting a new build, how can i take advantage of the
> > gigabytes of S/W tarballs i've collected for doing OE/yocto project
> > builds?
> >
> > i want to set the equivalent of a local mirror -- would i set a
> > value in the "Primary download site" config option, with the format
> > "file:///pathname/to/all/my/tarballs"?
>
> Take a look here:
> http://buildroot.org/downloads/manual/manual.html#_advanced_usage
> Section 8.11.4 describes a method for setting a download location via
> env or capturing it as part of a targets configuration.
i read that but it *seems* that that will simply use a shared
download directory for both download destination *and* tarballs you
need. what i'm after is the yocto project equivalent of a local source
mirror, and others have already insisted that there's no such thing in
buildroot.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
prev parent reply other threads:[~2015-04-20 13:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-15 20:42 [Buildroot] how to point at a massive local archive of S/W tarballs Robert P. J. Day
2015-04-20 12:55 ` Matthew Weber
2015-04-20 13:28 ` Robert P. J. Day [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=alpine.LFD.2.11.1504200926590.24210@localhost \
--to=rpjday@crashcourse.ca \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.