Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 13:33:28 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.11.1504161331240.2952@localhost> (raw)
In-Reply-To: <08725FB3-EB32-4438-9E8C-EE6113D8D022@gmail.com>

On Thu, 16 Apr 2015, Thomas De Schampheleire wrote:

> On April 16, 2015 7:07:32 PM CEST, "Robert P. J. Day" <rpjday@crashcourse.ca> wrote:
> >On Thu, 16 Apr 2015, Yann E. MORIN wrote:
> >
> >> 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).
> >
> >  ok, that answers the question, thanks very much.
>
> Using BR2_PRIMARY_SITE with scp to localhost is normally more easy than
> setting up a web server, assuming an ssh server is already running.
>
> That said, adding support for file:// in BR2_PRIMARY_SITE is trivial to add. In
> fact, I used to have such a patch in a much older buildroot version.

  i think that would be useful as i'm in the situation of wanting to
have a massive archive of S/W tarballs available for students in
various embedded linux classes that they can take advantage of for
their builds, but i (unsurprisingly) want that to be a read-only
directory so they can't make a mess of it or arbitrarily add anything
to it.

rday

-- 

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

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

  reply	other threads:[~2015-04-16 17:33 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
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 [this message]
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.1504161331240.2952@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