From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OpenEmbedded Development mailing list
<openembedded-devel@lists.openembedded.org>
Subject: doing a serious "distclean"
Date: Fri, 13 Nov 2009 09:56:32 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.0911130950150.29445@localhost> (raw)
as one of the posters mentioned earlier, bitbake's distclean doesn't
quite do a full cleaning. after bitbake'ing xterm, i have:
$ find . -name xterm-251*
./stamps/armv7a-angstrom-linux-gnueabi/xterm-251-r0.do_rm_work
./stamps/armv7a-angstrom-linux-gnueabi/xterm-251-r0.do_install
./stamps/armv7a-angstrom-linux-gnueabi/xterm-251-r0.do_build
./stamps/armv7a-angstrom-linux-gnueabi/xterm-251-r0.do_package_write
./stamps/armv7a-angstrom-linux-gnueabi/xterm-251-r0.do_package_stage_all
./stamps/armv7a-angstrom-linux-gnueabi/xterm-251-r0.do_package_write_ipk
./stamps/armv7a-angstrom-linux-gnueabi/xterm-251-r0.do_unpack
./stamps/armv7a-angstrom-linux-gnueabi/xterm-251-r0.do_compile
./stamps/armv7a-angstrom-linux-gnueabi/xterm-251-r0.do_package
./stamps/armv7a-angstrom-linux-gnueabi/xterm-251-r0.do_qa_staging
./stamps/armv7a-angstrom-linux-gnueabi/xterm-251-r0.do_patch
./stamps/armv7a-angstrom-linux-gnueabi/xterm-251-r0.do_fetch
./stamps/armv7a-angstrom-linux-gnueabi/xterm-251-r0.do_configure
./stamps/armv7a-angstrom-linux-gnueabi/xterm-251-r0.do_qa_configure
./stamps/armv7a-angstrom-linux-gnueabi/xterm-251-r0.do_rm_work_all
./stamps/armv7a-angstrom-linux-gnueabi/xterm-251-r0.do_populate_staging
./stamps/armv7a-angstrom-linux-gnueabi/xterm-251-r0.do_package_stage
./stamps/armv7a-angstrom-linux-gnueabi/xterm-251-r0.do_setscene
./stamps/armv7a-angstrom-linux-gnueabi/xterm-251-r0.do_distribute_sources
./deploy/glibc/sources/MIT-X/xterm/xterm-251.tgz
./deploy/glibc/sources/MIT-X/xterm/xterm-251.tgz.md5
./work/armv7a-angstrom-linux-gnueabi/xterm-251-r0
$
after "distclean"ing that package, what still remains is:
$ find . -name xterm-251*
./deploy/glibc/sources/MIT-X/xterm/xterm-251.tgz
./deploy/glibc/sources/MIT-X/xterm/xterm-251.tgz.md5
$
and, predictably, that tarball has been removed from the downloads
directory.
what would seem to be more useful is a bitbake clean command that
removes every single trace of a build from under the tmp directory,
but *leaves* the tarball in the download directory. that would
represent the best test for building a package from scratch, without
actually having to drag it down again, no? (or does such a bitbake
command already exist? "bitbake -c tmpclean"?)
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================
reply other threads:[~2009-11-13 14:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=alpine.LFD.2.00.0911130950150.29445@localhost \
--to=rpjday@crashcourse.ca \
--cc=openembedded-devel@lists.openembedded.org \
/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.