From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] pkg-download: support file:// in BR2_PRIMARY_SITE
Date: Tue, 17 Nov 2015 23:54:12 +0100 [thread overview]
Message-ID: <564BB014.6030809@mind.be> (raw)
In-Reply-To: <20151117175558.156ea1f0@free-electrons.com>
On 17-11-15 17:55, Thomas Petazzoni wrote:
> Dear J?r?me Pouiller,
>
> On Tue, 17 Nov 2015 17:07:58 +0100, J?r?me Pouiller wrote:
>> This feature was already discuted here:
>>
>> http://lists.busybox.net/pipermail/buildroot/2015-April/125419.html
>>
>> Personally, I have a big central directory with all tarballs I have
>> ever downloaded. I use this feature to isolate tarballs necessary to
>> build a configuration:
>>
>> make project_defconfig
>> make BR2_DL_DIR=/tmp/mirror-project BR2_PRIMARY_SITE=file:///home/user/dl source
>> tar -C /tmp -czvf mirror-project.tgz mirror-project
>
> You have a much simpler option:
>
> make external-deps
You probably mean:
for file in $(make external-deps); cp dl/$file /tmp/mirror-project; done
I think a local file PRIMARY_SITE can be useful for other situations as well,
e.g. a slow CIFS-mounted shared download location that is too slow to use as
DL_DIR, so I think the feature has merit.
Regards,
Arnout
>
> Thomas
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2015-11-17 22:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 16:07 [Buildroot] [PATCH] pkg-download: support file:// in BR2_PRIMARY_SITE Jérôme Pouiller
2015-11-17 16:55 ` Thomas Petazzoni
2015-11-17 22:54 ` Arnout Vandecappelle [this message]
2015-11-18 8:57 ` Thomas Petazzoni
2015-11-17 21:36 ` Arnout Vandecappelle
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=564BB014.6030809@mind.be \
--to=arnout@mind.be \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.