Neil Bothwick wrote: > On Tue, 11 Nov 2008 23:00:08 -0600, Dale wrote: > > >> Be very careful with --depclean. It can really mess up something if you >> are not watching close. >> > > That may have been the case some time ago, but depclean is much safer > now. Notice that the warning at the start of its output has disappeared > now? > > >
That is true but let's say a person updates python but forgets or doesn't know, to run python-updater, will --depclean know that? What if emerge doesn't work and they don't have buildpkg of some sort in make.conf? I agree that --depclean is a LOT better but there are still situations where it can mess up a system. It is best to be careful and really look at that list before letting it remove a package. Basically, don't type it in and walk off to let it do whatever it wants. I also seem to remember that big warning when --depclean runs. I think that may still be there for a reason. ;-) Dale :-) :-)
