From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC] *clean targets
Date: Wed, 07 Oct 2009 21:31:14 +0200 [thread overview]
Message-ID: <87bpkjknlp.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20091007183157.GD23847@mx.loc> (Bernhard Reutner-Fischer's message of "Wed\, 7 Oct 2009 20\:31\:57 +0200")
>>>>> "Bernhard" == Bernhard Reutner-Fischer <rep.dot.nop@gmail.com> writes:
Hi,
>> Sounds sensible. I would prefer to not touch the release target right
>> now, as I don't have xz installed, noone else needs it and I already
>> have my own release script signing the tarballs and uploading them.
Bernhard> There is no need for xz, if it doesn't exists then no .tar.xz
Bernhard> will be created.
Ahh yes, missed the || at the end of the line.
>> Makes sense. Why would we want to run the -clean targets of all the
>> individual packages first? That just tends to take ages (and fails on
>> buggy packages), and we're nuking the TARGET_DIR afterwards anyway.
Bernhard> calling the individual targets can be dropped, yes. I just
Bernhard> didn't remove Bernhard> it (yet).
OK. I notice now that your have rm -rf $(IMAGE) instead of
$(BINARIES_DIR). I guess we want the latter, as $(IMAGE) is just a
prefix, not a file name.
Bernhard> -dirclean: $(TARGETS_DIRCLEAN)
Bernhard> - rm -rf $(STAGING_DIR) $(TARGET_DIR) $(IMAGE) $(BUILD_DIR)/.root $(STAMP_DIR)
Bernhard> +# remove generated files, retain configs
Bernhard> +dirclean: clean $(TARGETS_DIRCLEAN)
Bernhard> + $(Q)rm -rf $(STAGING_DIR) $(HOST_DIR) $(TOOLCHAIN_DIR)
>>
>> Same comment about TARGETS_DIRCLEAN.
Bernhard> ack.
OK.
What about $(BUILD_DIR)? I guess we would want to delete that as well?
>> The git archive part is fine by me, but my script just expects the
>> .tar.gz, so I would like to keep it like that (for now atleast).
Bernhard> It would be nice if you could still pick it up and also sign/upload the .bz2
I do already:
ls *.bz2*
buildroot-2009.02-rc1.tar.bz2 buildroot-2009.05-rc3.tar.bz2
buildroot-2009.02-rc1.tar.bz2.sign buildroot-2009.05-rc3.tar.bz2.sign
buildroot-2009.02-rc2.tar.bz2 buildroot-2009.05.tar.bz2
buildroot-2009.02-rc2.tar.bz2.sign buildroot-2009.05.tar.bz2.sign
buildroot-2009.02-rc3.tar.bz2 buildroot-2009.08-rc1.tar.bz2
buildroot-2009.02-rc3.tar.bz2.sign buildroot-2009.08-rc1.tar.bz2.sign
buildroot-2009.02-rc4.tar.bz2 buildroot-2009.08-rc2.tar.bz2
buildroot-2009.02-rc4.tar.bz2.sign buildroot-2009.08-rc2.tar.bz2.sign
buildroot-2009.02.tar.bz2 buildroot-2009.08-rc3.tar.bz2
buildroot-2009.02.tar.bz2.sign buildroot-2009.08-rc3.tar.bz2.sign
buildroot-2009.05-rc1.tar.bz2 buildroot-2009.08.tar.bz2
buildroot-2009.05-rc1.tar.bz2.sign buildroot-2009.08.tar.bz2.sign
buildroot-2009.05-rc2.tar.bz2 buildroot-snapshot.tar.bz2
buildroot-2009.05-rc2.tar.bz2.sign
But the script generates it all from a single .tar.gz - Anyway, that's a
minor detail.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2009-10-07 19:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-07 16:24 [Buildroot] [RFC] *clean targets Bernhard Reutner-Fischer
2009-10-07 16:32 ` Sven Neumann
2009-10-07 18:12 ` Peter Korsgaard
2009-10-07 18:25 ` Bernhard Reutner-Fischer
2009-10-07 18:26 ` Peter Korsgaard
2009-10-07 18:31 ` Bernhard Reutner-Fischer
2009-10-07 19:31 ` Peter Korsgaard [this message]
2009-10-09 8:01 ` Thomas Petazzoni
2009-10-07 18:27 ` Peter Korsgaard
2009-10-09 7:51 ` Thomas Petazzoni
2009-10-09 8:00 ` Thomas Petazzoni
2009-10-09 9:48 ` Bernhard Reutner-Fischer
2009-10-09 11:28 ` Peter Korsgaard
2009-11-20 13:04 ` Peter Korsgaard
2009-11-20 15:28 ` Bernhard Reutner-Fischer
2009-11-20 15:55 ` Peter Korsgaard
2009-11-20 16:19 ` Bernhard Reutner-Fischer
2009-11-20 16:20 ` 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=87bpkjknlp.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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