| 1 |
On 01/24/2010 07:02 PM, Dale wrote: |
| 2 |
> Is there something that I am missing here? For me, system should |
| 3 |
> include the things needed for booting and for the package manager to |
| 4 |
> work. |
| 5 |
|
| 6 |
It should include the programs directly involved in booting, and the |
| 7 |
package manager. I'm not sure that it should contain their dependencies |
| 8 |
- since that information can be derived from the packages themselves. |
| 9 |
|
| 10 |
> As I pointed out in another reply, portage won't let you unmerge |
| 11 |
> itself but it will let you unmerge a package that will render portage |
| 12 |
> useless. |
| 13 |
|
| 14 |
Well, it shouldn't allow you to unmerge anything that will render |
| 15 |
ANYTHING useless without some explicit instruction to do so. |
| 16 |
|
| 17 |
The documentation does warn of this behavior: |
| 18 |
|
| 19 |
--unmerge (-C) |
| 20 |
WARNING: This action can remove important packages! Removes all |
| 21 |
matching packages. This does no checking of dependencies, so it |
| 22 |
may remove packages necessary for the proper operation of your |
| 23 |
system. Its arguments can be atoms or ebuilds. For a dependency |
| 24 |
aware version of --unmerge, use --depclean or --prune. |
| 25 |
|
| 26 |
If you use --depclean to remove your package then you're safe. |
| 27 |
|
| 28 |
Note - the command line option names are not well-chosen here. -C |
| 29 |
should really be --unmerge-without-checking-dependencies-unsafe or some |
| 30 |
other obnoxious option, and --depclean should be the easy to type parameter. |
Archives