sstate management

[Gary Thomas <gary@mlbassoc.com>]

I'm looking into using sstate more and in particular sharing
it amongst a number of builds.  I have a couple of questions
which I didn't find much info about.

* The sstate-cache for a given build/target seems to grow
   without bounds.  I have one build which I've been reusing
   since last November has grown to 62GB.  A very similar
   build which hasn't see quite so many 'bakes' is only 27GB.

   Is there some maintenance to be done on the sstate-cache?
   I'm thinking I want to set up a shared cache which might
   last for a long time and I would like to only keep the bits
   that are really needed.

* The second operational question I have is if I have a shared
   sstate cache and I make some sort of build, what is the best
   way (if any) to share any newly created objects so that my
   other builds can make use of them?

I've not actually tried to share any caches yet, so these
questions are just based on my rough understanding of the
use of sstate.  Please feel free to correct me if I've got
it [totally] wrong.

Thanks

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