Hi, another thing that might help is not generating the cache at all. It appears that we can get away with what is in /usr/portage/metadata/cache.
I've put -metadata-transfer into FEATURES to tell portage to skip the
"Generating cache" stuff, and added the following to my
/etc/portage/modules:
portdbapi.auxdbmodule = cache.metadata_overlay.database
I don't guarantee anything, but I've been using this approach for a
while (a year or so) and never had any problems.
I also am using squashfs+aufs for my portage tree, which - apart from
speeding things up here - has the nice little effect that /usr/portage
now only takes up about 50MB in a .sqfs image.
You will need to get aufs from the sunrise overlay, but if you are not
comfortable doing so you can use squashfs+unionfs as explained in this
gentoo-wiki article [1]
If you intend to use aufs, Martin Väth (who is also the current
maintainer of eix) has written a nifty little init-script for handling
those images (see "initscripts.tar.gz" on [2]).
HTH, Emil
[1]
http://gentoo-wiki.com/HOWTO_VERY_small_Portage_Tree_with_SquashFS_and_UnionFS
[2] http://www.mathematik.uni-wuerzburg.de/~vaeth/gentoo/index.html
--
Emil Beinroth
83059 Kolbermoor | Germany
Rich bachelors should be heavily taxed. It is not fair that some men should be
happier than others. -- Oscar Wilde
pgpIefaoI76sB.pgp
Description: PGP signature
