From: Robert P. J. Day <rpjday@crashcourse.ca>
To: buildroot@busybox.net
Subject: [Buildroot] how to point at a local archive of S/W tarballs?
Date: Thu, 16 Apr 2015 08:40:35 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1504160836530.19987@localhost> (raw)
In-Reply-To: <CAHXCMMKL_0tT08zgSgHhC9OVVJiTUdYe6USEasqY5PqygkPwVg@mail.gmail.com>
On Thu, 16 Apr 2015, Samuel Martin wrote:
> Hi Robert,
>
> On Thu, Apr 16, 2015 at 2:21 PM, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
> >
> > [apologies if you've seen this before -- i posted it yesterday but
> > it doesn't seem to show up in the ML archives.]
> >
> > 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"?
>
> You certainly want to set BR2_DL_DIR [1].
>
> [1] http://nightly.buildroot.org/#env-vars
i'm not convinced that's what i want ... AIUI, that variable defines
where the downloaded SW tarballs will be *placed*, and i'm happy to
leave that where it is as a local dl/ directory for the build.
what i want is to define a local (on-host) mirror for tarballs that
will be searched before going out to the net. i definitely don't want
the fetch process to try to *place* anything in that local mirror,
only to *fetch* from it.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next prev parent reply other threads:[~2015-04-16 12:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 12:21 [Buildroot] how to point at a local archive of S/W tarballs? Robert P. J. Day
2015-04-16 12:29 ` Samuel Martin
2015-04-16 12:40 ` Robert P. J. Day [this message]
2015-04-16 12:58 ` Samuel Martin
2015-04-16 13:17 ` Robert P. J. Day
2015-04-16 17:05 ` Yann E. MORIN
2015-04-16 17:07 ` Robert P. J. Day
2015-04-16 17:27 ` Thomas De Schampheleire
2015-04-16 17:33 ` Robert P. J. Day
2015-04-16 17:39 ` Yann E. MORIN
2015-04-16 17:33 ` Yann E. MORIN
2015-04-20 20:17 ` Peter Korsgaard
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.1504160836530.19987@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox