[yocto] Safely cleaning 'downloads'
Laurentiu Palcu
laurentiu.palcu at intel.com
Fri Oct 2 04:43:37 PDT 2015
Hi Garry,
It's probably a little late (I'm not reading the Yocto mailing lists
very often now) but sometime ago I ran out of space myself and I wrote
this script that I sent out on oe-core mailing list. It did the job for
me. For some reason it didn't make it in master but maybe you find it
useful.
I didn't test it since then though. Maybe things changed, I don't know.
Give it a try if you wish. If you want to play safe, I recommend making
a copy of your downloads directory (if you have space left). :)
http://lists.openembedded.org/pipermail/openembedded-core/2015-June/106026.html
laurentiu
On Wed, Sep 30, 2015 at 06:13:39AM -0600, Gary Thomas wrote:
> 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
> ------------------------------------------------------------
> --
> _______________________________________________
> yocto mailing list
> yocto at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
More information about the yocto
mailing list