-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 *if* you move /usr/portage to something like reisterfs, you will get better performacem even on slower machines. my PIII/800 can update the cache in ~ 3 minutes now .... ext3 just doesn't cut it in a busy tree like portage ... the filesystem just isn't quick enough .... there are some other things you can do like using xfs/jfs for /usr/portage/distfiles and what not, but that' just a start. First thing is first, fix portage, then if you like, contact me off list and I can help you tweak emerge so it runs a little quicker and still be safe :D
John J. Foster wrote: | I unmasked portage-2.2_pre4 to see if it would help with the extreme | slowness of portage updating of its cache during a sync. I had also | previously emerged cdb to try to help with that also. Anyway, I'm not | really sure what state my portage is in right now, except that now every | emerge command returns | | [EMAIL PROTECTED] ~ $ emerge --info | Traceback (most recent call last): | File "/usr/bin/emerge", line 31, in ? | import emergehelp, xpak, commands, errno, re, socket, string, time, types | File "/usr/lib/portage/pym/emergehelp.py", line 7, in ? | from portage_const import PRIVATE_PATH,PRELINK_BINARY,HASHING_BLOCKSIZE | File "/usr/lib/portage/pym/portage_const.py", line 7, in ? | from portage_const import PRIVATE_PATH,PRELINK_BINARY,HASHING_BLOCKSIZE | ImportError: cannot import name PRIVATE_PATH | | I already tried | http://www.gentoo.org/proj/en/portage/doc/manually-fixing-portage.xml | but it didn't help. Me thinks I should have done a quickpkg! | | Any help greatly appreciated. | | Thanks, | festus -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFH3dGY8hUIAnGfls4RApvUAJ9pK3wWqS5LpwvRtCOfzrItpxxtDgCgjdJm mgZu5SRDPda51qAuZtX58RE= =8DRz -----END PGP SIGNATURE----- -- gentoo-user@lists.gentoo.org mailing list
