From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] pkg-download: support file:// in BR2_PRIMARY_SITE
Date: Wed, 18 Nov 2015 09:57:27 +0100 [thread overview]
Message-ID: <20151118095727.08b48388@free-electrons.com> (raw)
In-Reply-To: <564BB014.6030809@mind.be>
Arnout, J?r?me,
On Tue, 17 Nov 2015 23:54:12 +0100, Arnout Vandecappelle wrote:
> >> 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
Yes, indeed, I only pointed at "make external-deps", leaving it to the
reader to figure out how to make use of it in the context of what
J?r?me is trying to do. But I could have been more explicit.
> 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.
Yes, I also think the feature has merit.
J?r?me, could you respin the patch after updating the Config.in help
text of the BR2_PRIMARY_SITE option?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-11-18 8:57 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
2015-11-18 8:57 ` Thomas Petazzoni [this message]
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=20151118095727.08b48388@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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