From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] how to point at a local archive of S/W tarballs?
Date: Mon, 20 Apr 2015 22:17:15 +0200 [thread overview]
Message-ID: <871tjev9kk.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20150416173330.GC4405@free.fr> (Yann E. MORIN's message of "Thu, 16 Apr 2015 19:33:30 +0200")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
Hi,
>> 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.
> Well, I was thinking of this, too, but I really wonder if that makes
> sense: archives are copied from the primary, so you'd end up with
> duplication locally.
> Unless we're playing it smart and make symlinks.
> But then what would happen if the archive disapear from primary?
I would prefer to keep it dumb and simple. The typical usecase for
BR2_PRIMARY_SITE is imho just to use to local mirror for download speed
/ reliability reasons (that's atleast what I have used it for).
I don't feel strongly for/against file:// support, but if there's a
desire to add it ..
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2015-04-20 20:17 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
2015-04-16 17:33 ` Yann E. MORIN
2015-04-20 20:17 ` Peter Korsgaard [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=871tjev9kk.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--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