From: MikeW <mw_phil@yahoo.co.uk>
To: buildroot@busybox.net
Subject: [Buildroot] Persistent tarball repository
Date: Wed, 1 Nov 2006 15:46:32 +0000 (UTC) [thread overview]
Message-ID: <loom.20061101T164136-413@post.gmane.org> (raw)
In-Reply-To: 1162394701.2945.4.camel@iridium.gnat.ca
Nathanael D. Noblet <nathanael@...> writes:
>
> On Wed, 2006-11-01 at 14:23 +0000, MikeW wrote:
> > I found to my annoyance that 'make distclean' clears out
your downloaded .tar.gz
> > files in /dl, which could be a pain if you hadn't realised
that (and was, since
> > there appears to be a problem with ftp.kernel.org
so I got the file 'manually')
> >
> > May I ask if there is a setting to allow these files
to be cached somewhere that
> > 'distclean' doesn't clear out ?
> > Might also be useful on a server in a team environment
to ensure everyone
> > uses the same reference downloads without local duplication
and time penalty.
>
> make clean?
Yes, but 'make clean' only removes object files, causing a straight rebuild from
source, 'distclean' is supposed to remove any make-generated/config files as
well - IIRC.
Which is not quite the same as deleting all your patiently downloaded
tarballs as well !
So I just wondered if there was a way to either allow distclean to spare
the package source files, or alternatively, if you could 'get' from a
local repository rather than having to download via FTP/HTTP, if your
required file existed.
Regards,
MikeW
next prev parent reply other threads:[~2006-11-01 15:46 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 [this message]
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 ` [Buildroot] Persistent tarball repository 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=loom.20061101T164136-413@post.gmane.org \
--to=mw_phil@yahoo.co.uk \
--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.