On Monday 17 November 2003 13:42, Renat Golubchyk wrote: > On Monday 17 November 2003 04:55, Jason Stubbs wrote: > > On Monday 17 November 2003 10:51, Luke Scharf wrote: > > > On Sun, 2003-11-16 at 19:31, Stroller wrote: > > > > On Nov 16, 2003, at 8:03 pm, Luke Scharf wrote: > > > > > 4. Emerge -- does unmerge remove the files from the system? > > > > > > > > I always use `emerge -C some-package`, but someone else will be along > > > > shortly with a safer option. > > > > > > According to the man page, that's the official way to do it! > > > > > > "emerge unmerge " == "emerge -C " > > > > "emerge unmerge" != "emerge -C" > > "emerge clean" == "emerge -C" > > Hmm, it's actually the other way round. From the manpage: > clean (-c) > Cleans the system by removing packages that will not effect the > functionality of the system. The arguments can be ebuilds, classes, or > dependencies. For example, emerge clean binutils cleans out old > versions of binutils; emerge clean net-www/mozilla-0.9.9-r2 cleans out that > specific version of Mozilla. This is generally safe to use. Note that clean > does not remove unslotted packages. > unmerge (-C) > WARNING: This action can remove important packages! Removes all matching > packages. This does no checking of dependencies, so it may remove > packages necessary for the proper operation of your system. Its arguments > can be ebuilds, classes, or dependencies -- see clean above for examples.
Hmmm.. yeah you're right. I was wondering why nobody else had said anything. I didn't notice the difference between the -c and the -C. Thanks for clearing that up! For the record, I don't use either of them. I have AUTOCLEAN=yes and always use unmerge instead of -C. Forgive my misunderstanding. Jason -- [EMAIL PROTECTED] mailing list
