On 2012.03.28 20:04, Rich Freeman wrote: > On Wed, Mar 28, 2012 at 2:53 PM, Christoph Mende <ange...@gentoo.org> > wrote: > > > > I believe it's /var/lib/<name>. Here's what FHS says: > > /var/cache is intended for cached data from applications. Such data > is > > locally generated as a result of time-consuming I/O or calculation. > > The application must be able to regenerate or restore the data. > Unlike > > /var/spool, the cached files can be deleted without data loss. > > > > I can do rm -rf /usr/portage ; mkdir /usr/portage ; emerge --sync and > it will work just fine, I think.
That's pretty much what happened in a stage1 or stage2 install. Its not cache though as you don't get back the same data as was deleted. Think 6 month old install. > > That really does point to cache. The only thing different from a > browser cache is that portage doesn't automatically refresh it. > > distfiles and packages are the same (well, depending on where you get > your binpackages from, that might or might not be a cache per-se - if > you're just using FEATURES=buildpkg then you can do an emerge -e > world > and get it back). Nope. If you have just done rm -rf /usr/portage ; mkdir /usr/portage ; emerge --sync, then emerge -e world gets you the equivelent of emerge --sync && emerge world -uDN Even if you haven't fetched a new tree, you have lost all your old binary packages, which you were keeping in case of a broken ~arch upgrade that needs to be reverted in a hurry. e.g. one of the nice big shiny packages that emerge -e world just updated for you. [snip] > > Rich > > > -- Regards, Roy Bamford (Neddyseagoon) a member of elections gentoo-ops forum-mods trustees
