| 1 |
Neil Bothwick schrieb: |
| 2 |
> On Mon, 4 May 2009 10:45:00 +0100, Matt Causey wrote: |
| 3 |
> |
| 4 |
>> Sooo, my question. What is the expected behaviour here? Are the |
| 5 |
>> ebuilds intended to maintain knowledge of the files they put on a |
| 6 |
>> system, so they can remove the binaries when --unmerge'd? Are kernel |
| 7 |
>> modules handled differently because of the possibility of damaging a |
| 8 |
>> working system? |
| 9 |
> |
| 10 |
> The latter. The user programs will be gone but the kernel modules stay. |
| 11 |
> With more "normal" packages, the only files that are not removed are |
| 12 |
> those in CONFIG_PROTECTed directories and those that have been modified |
| 13 |
> since installation. |
| 14 |
> |
| 15 |
> |
| 16 |
|
| 17 |
Anyway you also might want to run an emerge --depclean -av after |
| 18 |
unmerging. Maybe there are othere programs not needed anymore at now. |
| 19 |
|
| 20 |
kh |
Archives