Dave Nebinger wrote: >> emerge portage >> etc-update [...] > >> emerge --update --deep --newuse world > > > You don't need --newuse unless you changed your use flags in /etc/make.conf.
This is not totally true, default useflag changes because "emerge --sync" update profiles or because you 've installed a particular package. This mean that after an emerge --sync sometimes run emerge --update --deep --newuse world is needed *twice* not only one time (this to be on the safer side) >> emerge -p depclean > > > Some folks do this, others recommend against it as a removal of some package > sometimes could break if there are unknown dependencies against it. I > choose not to because I have only installed those packages I needed and > shouldn't have any fluff. Personally I reccommend this, more because it can be used as a diagnosis tool than to keep the system clean. Don't ask how it's happened but at least one time it show me that my *whole* world was not needed -> fixed it with emerge "--noreplace <big list>" Summa, use it, check twice what it show, if you don't know what it's removing read it to world file with "emerge -uDpv --noreplace <package>" [...] > >> revdep-rebuild > > > Don't know that you need to do this, either. needed after a lot of updates, generally libraryes used from other packages. It can bother you with packages in /opt . make it ignore those. [...] > > >> reboot (this to make sure that the update didn't break anything, make >> sure all services start as intended, etc. - not because Linux >> needs an update for changes to take effect!) if you updated "grub" or before the reboot reinstall it: # grub setup (hd0) root (hd0,0) ^^ modify as needed anyway at a reboot I prefere the trick mentioned from "Graham Murray" in this same thread [...] -- No problem is so formidable that you can't walk away from it. ~ Charles M. Schulz But sometimes run fast is better ~ Francesco R. -- gentoo-user@gentoo.org mailing list
