From: Marc Lindahl <marc@bowery.com>
To: buildroot@busybox.net
Subject: [Buildroot] Persistent tarball repository
Date: Wed, 1 Nov 2006 12:17:14 -0500 [thread overview]
Message-ID: <1a2b58b88744ef4e337f310b1b5b0c3a@bowery.com> (raw)
In-Reply-To: <1f11a5490611010841n3a71baeei8d55aa4dc7251330@mail.gmail.com>
BR2_DL_DIR already there no patch needed... why do you need to move it
around so much it needs to be in menuconfig?
also I disagree with patching distclean, then it will not behave the
way all other distcleans everywhere behave. Make a new option instead
(though for the life of me I can't figure out what you'd need it for)
my $0.02,
Marc
On Nov 1, 2006, at 11:41 AM, Ashwin Bihari wrote:
> On 11/1/06, MikeW <mw_phil@yahoo.co.uk> wrote:
>>
>> 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_______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/enriched
Size: 1438 bytes
Desc: not available
Url : http://busybox.net/lists/buildroot/attachments/20061101/38ba48dd/attachment.bin
next prev parent reply other threads:[~2006-11-01 17:17 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 [this message]
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=1a2b58b88744ef4e337f310b1b5b0c3a@bowery.com \
--to=marc@bowery.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