On 11/7/05, Jarry <[EMAIL PROTECTED]> wrote: > http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=1#doc_chap3 > ======================== <copy&paste>===================== > Updating your System > To keep your system in perfect shape (and not to mention install the > latest security updates) you need to update your system regularly. Since > Portage only checks the ebuilds in your Portage tree you first have to > update your Portage tree. > > Code Listing 2: Updating the Portage tree > # emerge --sync > > When your Portage tree is updated, you can update your system with > emerge --update world > ... > Code Listing 16: Removing orphaned dependencies > # emerge --update --deep --newuse world > # emerge --depclean > # revdep-rebuild > ============================================================ > > Could some of you, gentoo-wizards, be kind enough and explain, what > is wrong in doing the things the way gentoo handbook recommends it? > Without offensive language, if I may ask...
The idea is very simple: some upgrades are not compatible with what you have previously installed. A very good example will be the recent change to Apache. The configuration files moved. A lot of people who blindly upgraded due to either seeing but not reading, or cron jobs had their system borked. To make things worse, they started whining, in the forums, on the ML, and probably other places. When maintaining a system, it is good to know what each upgrade does, and take necessary precautions. The devs can have the ebuild to print out warning messages, but will your cron be able to catch it? To elabrate even more: Redhat, suse and possibly other distro users can do cron upgrades, as those distros never give out in-compatible upgrades to a release. Those upgrades will wait until the next release, where everything is upgraded, and the users will need to re-install the whole system and possible pay more for the next release. Things are done differently here in Gentoo, everything is dynamic, a carefully carried out upgrade can bring a 1.4 to current, which is amazing I have to say. Because of this, it is inevitable that some upgrades will not be compatible. Whilst the devs made every effort to keep you warned/informed, it is *your* responsibility to carry out the upgrades properly. And a cron job simply isn't the proper way. Hope I made the reason clear enough. Finally, please don't get offended. We were not meant to do that. Try dig out your sense of humour, :P -- Joe -- There are 3 kinds of people in the world: Those who can count, and those who can't. -- gentoo-user@gentoo.org mailing list
