Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Andreas Oberritter <obi@opendreambox.org>
To: Kang Kai <kai.kang@windriver.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: cleanup-workdir
Date: Thu, 12 Apr 2012 20:47:26 +0200	[thread overview]
Message-ID: <4F87233E.2030604@opendreambox.org> (raw)

Hello Kai,

because I was low on disk space, I just tried scripts/cleanup-workdir
for the first time. My observations:

1.) It deletes work directories that were built for other machines
(archs) than the current one. I guess the list of architectures to
handle should be queried from bitbake to avoid this.
2.) It doesn't delete work directories of previously deleted recipes.

Regards,
Andreas



             reply	other threads:[~2012-04-12 18:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-12 18:47 Andreas Oberritter [this message]
2012-04-13  1:49 ` cleanup-workdir Kang Kai
2012-04-13  9:47   ` cleanup-workdir Andreas Oberritter
2012-06-02 15:37     ` cleanup-workdir Bob Cochran

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=4F87233E.2030604@opendreambox.org \
    --to=obi@opendreambox.org \
    --cc=kai.kang@windriver.com \
    --cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox