Now another question (and one I should probably know but dont), is fixpackages automatically run after every emerge sync? And if not, is it a bad idea (EG could be problematic, or a waste of time) to run it afterwords by hand (EG emerge sync && fixpackages)_________________{ NO -U } { STRIP }
{ TINY }

So, it would seem like a design blunder . I mean, who would embed a couple of bytes long string to be updated into a several megabytes compressed files (with bzip2 above all)? Is finding a solution that complicated?

No offence meant. We all make mistakes when developping softwares. You can't always predict everything that some peace of code will need to deal with in the future (altough that in this case, I would find it rather embarrassing).

What I'm wondering is, why isn't fixpackages keeping track of what it updated and what it did not. fixpackages takes about 40 minutes to run on my system. When it's done and I run the command right back, it will take... well, 40 minutes to execute. Obviously, fixpackages is quite... dumb (in the sense that it's not intelligent). Not everybody has a 2Ghz dual P4 bombs _________________(7 of 9) Installing star-trek/species-8.4.7.2::talax.