On Tue, 1 Nov 2011 19:00:04 +0100 meino.cra...@gmx.de wrote: > Urs Schutz <u.sch...@bluewin.ch> [11-11-01 18:04]: > > On Tue, 1 Nov 2011 04:45:25 +0100 > > meino.cra...@gmx.de wrote: > > > > > Hi, > > > > > > I know of three commands to check the consistency of a > > > Gentoo system: > > > > > > > > > eix-sync && emerge --color=n -p -v --newuse > > > --update --deep world emerge -p -v --depclean > > > revdep-rebuild --ignore -p -v > > > > > > of course, one has to remove the -p and -v flags after > > > checking the putput of the commands. > > > > > > What else can be checked and should be checked from > > > time to time or after each update? > > > > > > Thank you very much in advance for any help! > > > > > > Best regards, > > > mcc > > > snip... <> snip... > > Hi, > > thank you all very much for the checks listed. > > One question remains: > What sequence of commands is adviced to guarantee > the best effect on the one hand and on the other hand > not to be urged to recompile things -- especially > those like libreoffice...-- twice and more? > > Thank you very much in advance for your help! > Best regards, > mcc > >
Portage is clever, and does not build libreoffice twice, even if you change the sequence. Some binary packages are faster to install. I'm pretty happy with the prebuilt version of libreoffice. If you stay with stable packets there is less rebuilding of heavy packages, as they normally get less updates. The sequence depends on what use you have. I would do it differently on a server 1000 km away, but anyway here is what I do normally on my laptop: > eix-sync then learn about the new packages in portage, look for what gets updated. Then > emerge -uDpvtN world to see if there is any blockers, licenses or any other inconsistencies which need to be resolved manually first (running a mix of stable and unstable packages here, so this happens from time to time). Then portage may work in the background, while I do my usual work on the laptop (all on one line): > emerge -uDN world && revdep-rebuild -i && cfg-update -u && elogv When the ventilator noise stops and cpu temperatures drop I check the yellow and red elogv output lines, and if there is something indicated by the package maintainers I do it right away. I simply delete the green elogv output lines. Sometimes I do a > emerge --depclean -p more because portage says that one should do it. I feel that it is a lot of work to go through the package list manually and do not see the immediate benefit in doing it often. When I remove packages, I always do > emerge -uDN world && revdep-rebuild -i && elogv as I don't trust the state of the system after removing packages. > eix-test-obsolete -d is easy if it is done often, as there is little corrective action to do on a day to day basis. > eclean-dist -d -p This is really fast and painless, if you do not need old package sources. > glsa-check -t all should find no problems if you have an up to date installation. > eselect news list and > eselect news read xx is always a good thing to do and helps you to prevent the big problems with a evolving Gentoo installation. If there is a day without portage updates for your packages you could do > emerge -uDN --complete-graph --with-bdeps=y world or > rkhunter or > smartctl --all /dev/sda or > freshclam && clamscan or build a new kernel, just to have some fun... Sometimes I get a little jealous when I see my nephew installing programs and updating applications in Ubuntu... Regards Urs
