Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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:39:44 +0200	[thread overview]
Message-ID: <20150416173943.GD4405@free.fr> (raw)
In-Reply-To: <alpine.LFD.2.11.1504161331240.2952@localhost>

Robert, All,

On 2015-04-16 13:33 -0400, Robert P. J. Day spake thusly:
> On Thu, 16 Apr 2015, Thomas De Schampheleire wrote:
[--SNIP--]
> > 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.

Well, how would those students reach that location? NFS?

Would it not make much more sense to share that location via HTTP and
use that as the primary, so you know they won;t be able to write
anything in there?

I think this is typically a case where the primary (over HTTP) is indeed
a good solution. And as I replied to Thomas, running a *simple* webserver
is pretty easy. Granted, there's no access control, no fancy stuff but
directory listing and file download (no fancy PUT, POST COL and stuff),
but that's basically just what you need 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.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2015-04-16 17:39 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
2015-04-16 17:39                 ` Yann E. MORIN [this message]
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=20150416173943.GD4405@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