Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ashwin Bihari <abihari@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Persistent tarball repository
Date: Wed, 1 Nov 2006 10:41:02 -0600	[thread overview]
Message-ID: <1f11a5490611010841n3a71baeei8d55aa4dc7251330@mail.gmail.com> (raw)
In-Reply-To: <loom.20061101T171522-277@post.gmane.org>

On 11/1/06, MikeW <mw_phil@yahoo.co.uk> wrote:
>
> Yes - I think my issue is that the downloads are held 'within' the
> buildroot
> tree, hence the semantics of distclean as you describe them mean that they
> must go.
>
> If they were outside the buildroot tree, then I guess distclean ought not
> to clear them out.
>
> Wonder if that's the making of a patch - only 'distclean' delete
> downloaded tarballs if they occur under the buildroot directory;
> but currently there's no menuconfig option to say where downloads are kept
> ...
> however at the moment I just want something that 'works out of the box'!
>
> Thanks,
> MikeW
>

Mike,

By all means provide a patch that allows you to change the location of the
DL directory and whether or not it should be deleted during a distclean. I
would definitely find it useful and if others agree, it might get committed.

Regards

-- 
~ Ashwin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://busybox.net/lists/buildroot/attachments/20061101/d24358a4/attachment.htm 

  reply	other threads:[~2006-11-01 16:41 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 [this message]
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=1f11a5490611010841n3a71baeei8d55aa4dc7251330@mail.gmail.com \
    --to=abihari@gmail.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