In my experience, you may get away with this regime for a short time on an almost new system, but it will almost invariably break an older system (due to "emerge depclean")
The safest/most reasonable order is emerge sync glsa-check -l|grep "\[N" glsa-check -f AnyPackagesReportedAbove revdep-rebuild restart deamons This gives you a stable, up to date system security wise with minimal chance of breakage If you want to go further with little increased risk: emerge world -uvp check for gotchas and packages that may cause grief, and those that have daemons that need restarting emerge world -u revdep-rebuild The next step is for the masoschists: emerge world -uDvp check as above emerge world -uD On all my systems this step has the most pain for the least gain. Again newer systems seem to have few problems, but older systems with large package counts (>1000) need a lot of frustrating work for what I see as little benefit. Lastly, I think "emerge depclean" has to rank up towards the top of the ways to kill a gentoo system. Its not so much that it can remove critical packages, its the fact that newbies see it and say "wow, it will keep the crud down" - but they usually do not know what is critical and what is not! Result a dead system and a resinstall. Personally I run revdep-rebuild only occasionally as it doesnt often pick things up. --deep just doesnt work on my older systems due to conflicting packages. Maybe if I run it everytime it will never get to this state, but I found I was building fixing systems more than using them! My oldest system started at gentoo 1.1a (I think), and my desktop at 1.1b - both have been through hardware upgrades, in some cases moving the whole install to new disks, from raid to LVM and recovered from things like "rm -rf /usr/portage" (yes you can come back from this) amongst other disasters - but both can still be traced back to the original install. So the above strategy has been proven to work for the long term. Recently, I have started to just do security upgrades during the teaching semesters (when it *must* work all the time!), and leaving the more troublesome major upgrades to the breaks - this has saved a lot of work as well as given improved reliability when I need it. Have fun, BillK On Fri, 2005-04-22 at 09:11 +0000, [EMAIL PROTECTED] wrote: > I have no software I need to install, but just wish to make sure my > system is up to date. I'm happy to allow this to run for as long as > needed. As near as I could tell from the documentation, the order would > be something like this: > > emerge portage > etc-update > emerge --sync // is this necessary if followed by an emerge update? > > emerge --update --deep --newuse world > > emerge -p depclean > emerge gentoolkit > revdep-rebuild > > etc-update > etc-update // yes, twice > > 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!) > > Thanks! -- William Kenworthy <[EMAIL PROTECTED]> Home! -- [email protected] mailing list
