From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] how to point at a local archive of S/W tarballs?
Date: Thu, 16 Apr 2015 19:05:25 +0200 [thread overview]
Message-ID: <20150416170525.GA4405@free.fr> (raw)
In-Reply-To: <alpine.LFD.2.11.1504160912290.18180@localhost>
Robert, All,
On 2015-04-16 09:17 -0400, Robert P. J. Day spake thusly:
[--SNIP--]
> i know, i referred to that very config option in my original
> posting. what i'm wondering is if that config option -- "Primary
> download site" -- can be set to point at a local directory on my build
> host that's already loaded with S/W tarballs i've built up over the
> months for use with my OE and yocto builds.
>
> the help for that option says only that, "Valid URIs are URIs
> recognized by $(WGET) and scp URIs of the form
> scp://[user@]host:path." last time i looked, wget doesn't support the
> "file://" form of URI, so i can't use that.
>
> is there a standard way to do this?
Short answer: no.
Long answer:
BR2_DL_DIR is used both as a way to look for existing download, and as
the location where new downloads will be stored.
So, if you set (in the menuconfig or on the command line)
BR2_DL_DIR=/path/to/your/local/cache it will be looked into for existing
archives, and Buildroot will also store the ones it downlaods on its on
there.
If you really, really wish no to shared the download location, you could
get to run a simple webserver locally that you would use as a primary.
But then Buildroot would also store the archives it downloads from the
primary in its own dl/ dir (hence duplication in that case).
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2015-04-16 17:05 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
2015-04-16 12:58 ` Samuel Martin
2015-04-16 13:17 ` Robert P. J. Day
2015-04-16 17:05 ` Yann E. MORIN [this message]
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=20150416170525.GA4405@free.fr \
--to=yann.morin.1998@free.fr \
--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