| 1 |
Hi! |
| 2 |
|
| 3 |
On Tuesday 29 October 2002 10:06, Sven Vermeulen wrote: |
| 4 |
> emerge clean doesn't do anything to your system, it only removes |
| 5 |
> ebuild-files from _your_ portage-tree that aren't available anymore on |
| 6 |
> the rsync-server(s) (and thus aren't really in Gentoo anymore). |
| 7 |
|
| 8 |
Not at all. From "man emerge": |
| 9 |
|
| 10 |
clean (-c) |
| 11 |
Cleans the system by removing packages that will not effect the |
| 12 |
functionality of the system. The arguments can be ebuilds, classes, or |
| 13 |
dependencies. For example, emerge clean binutils cleans out old versions |
| 14 |
of binutils; emerge clean net-www/mozilla-0.9.9-r2 cleans out that |
| 15 |
specific version of Mozilla. This is generally safe to use. Note that |
| 16 |
clean does not remove unslotted packages. |
| 17 |
|
| 18 |
So if there are foobar-1.0 and foobar-1.1 installed and they are in the |
| 19 |
same slot, "emerge clean" will safely unmerge foobar-1.0. |
| 20 |
|
| 21 |
> Your missing .so-files have an other cause... |
| 22 |
|
| 23 |
ACK. |
| 24 |
|
| 25 |
Markus |
| 26 |
-- |
| 27 |
"We can debug relationships, but it's always good policy to |
| 28 |
consider the people themselves to be features. People get annoyed |
| 29 |
when you try to debug them." ( Larry Wall ) |
Archives