On Thursday 18 November 2004 02:32, Shawn wrote: > Be VERY VERY careful when you do an emerge world down the road. I just had > this bite me bad - and I even took all the "right" steps. By "right" > steps, I'm referring to a practice emerge (-p) first, and seeing what would > get updated, modifying your USE flags to get rid of packages you don't > need/want, doing the emerge, running etc-update or dispatch-conf and > examining the differences of EVERY updated config file and taking care not > to overwrite your modified files.
You can simply comment things out of the world file, and then they'd be ignored. If you're REALLY paranoid, you could also create packages using quickpkg. This will create a binary package of X on your machine that you can revert to if neccessary. This is hugely beneficial if you need to be able to revert back to something of a version that's either been masked or pruned from the portage tree. (It also lets you emerge once on 1 machine, and install packages on others (assuming the same configuration (make.conf) on the other machines)) > > I did all of that, and still ended up with a conflict when two > complimentary packages were updated but did not cooperate together > (specifically Perl and qmail-scanner, and maybe clamav). > > Otherwise, my update seems to have been rather thorough... > > Shawn _______________________________________________ clug-talk mailing list [EMAIL PROTECTED] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
