From: Peter Korsgaard <peter.korsgaard@barco.com>
To: buildroot@busybox.net
Subject: [Buildroot] Persistent tarball repository
Date: Mon, 06 Nov 2006 14:30:06 +0100 [thread overview]
Message-ID: <87y7qozorl.fsf@sleipner.barco.com> (raw)
In-Reply-To: <loom.20061101T151612-639@post.gmane.org> (MikeW's message of "Wed, 1 Nov 2006 14:23:36 +0000 (UTC)")
>>>>> "Mike" == MikeW <mw_phil@yahoo.co.uk> writes:
Hi,
Mike> May I ask if there is a setting to allow these files to be
Mike> cached somewhere that 'distclean' doesn't clear out ? Might
Mike> also be useful on a server in a team environment to ensure
Mike> everyone uses the same reference downloads without local
Mike> duplication and time penalty.
We use a shared dl directory on a NFS server (setting
BR2_DL_DIR). Make distclean doesn't delete that.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2006-11-06 13:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-01 14:23 [Buildroot] Persistent tarball repository MikeW
2006-11-01 15:25 ` Nathanael D. Noblet
2006-11-01 15:46 ` MikeW
2006-11-01 16:01 ` Ashwin Bihari
2006-11-01 16:23 ` MikeW
2006-11-01 16:41 ` Ashwin Bihari
2006-11-01 17:17 ` Marc Lindahl
2006-11-01 17:25 ` Bernhard Fischer
2006-11-01 17:47 ` [Buildroot] Persistent tarball repository - already exists MikeW
2006-11-06 13:30 ` 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=87y7qozorl.fsf@sleipner.barco.com \
--to=peter.korsgaard@barco.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