All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Yocto Project <yocto@yoctoproject.org>
Subject: Safely cleaning 'downloads'
Date: Wed, 30 Sep 2015 06:13:39 -0600	[thread overview]
Message-ID: <560BD1F3.1090907@mlbassoc.com> (raw)

Over time, I tend to build in the same build tree many, many
times.  This leads to some really big trees as many things are
duplicated, especially in the 'downloads' directory.

I use local mirrors and hence my 'downloads' directory is
_mostly_ populated with symbolic links.  However, there are
also expanded SCM packages, e.g. git2/xxx

How can I safely clean up the 'downloads' directory?  I already
copy any created tarballs (I use BB_GENERATE_MIRROR_TARBALLS="1"
to preclude unneeded downloads) to my mirror, but I'd like to
periodically clean out the whole directory (without disturbing
my builds of course).  I've found out the hard way that just
emptying seems to be unsafe, at least for some recipes like
the [RaspberryPi] Linux kernel recipe which once built seems
to expect the expanded git2/xxx tree to remain.

Just trying to find ways to recover my lost GB...

Thanks for any ideas

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


             reply	other threads:[~2015-09-30 12:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-30 12:13 Gary Thomas [this message]
2015-10-01 16:38 ` Safely cleaning 'downloads' Smith, Virgil
2015-10-01 16:49   ` Gary Thomas
2015-10-01 16:54     ` Christopher Larson
2015-10-01 17:12       ` Martin Jansa
2015-10-01 17:49       ` Gary Thomas
2015-10-02 11:43 ` Laurentiu Palcu

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=560BD1F3.1090907@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=yocto@yoctoproject.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.