1 |
On Wed, 2014-11-05 at 20:59 +0000, Neil Bothwick wrote: |
2 |
> On Tue, 04 Nov 2014 18:01:57 -0600, Dale wrote: |
3 |
> |
4 |
> > For future reference, make sure nothing depends on whatever version of |
5 |
> > python you want to remove before you remove it. If you don't, it could |
6 |
> > get very interesting in a really bad way. |
7 |
> |
8 |
> The simplest way to do that, with any package you want to remove, is to |
9 |
> use |
10 |
> |
11 |
> emerge --depclean --ask -v cat/pkg |
12 |
> |
13 |
> instead of |
14 |
> |
15 |
> emerge --unmerge --ask cat/pkg |
16 |
> |
17 |
> With depclean, dependencies are checked and the package will only be |
18 |
> removed if nothing depends on it. Adding the -v shows you what depends on |
19 |
> it. |
20 |
|
21 |
It should also be noted that running --depclean on a specific package |
22 |
*ONLY* removes that package. After depcleaning a specific package, you |
23 |
should run --depclean again to remove any dependencies of that removed |
24 |
package: |
25 |
|
26 |
emerge --depclean --ask -v cat/pkg |
27 |
emerge --depclean --ask |
28 |
|
29 |
The alternative (at least for packages not in a selected set) is to |
30 |
|
31 |
emerge --deselect cat/pkg |
32 |
emerge --depclean --ask |
33 |
|
34 |
This will, oddly enough, deselect the package from being wanted or |
35 |
"selected", allowing it to be depcleaned, along with its own |
36 |
dependencies, if no other packages depend on it. |
37 |
|
38 |
Both methods require two commands, so mostly there's no real difference; |
39 |
and in this case depcleaning python:$SLOT is probably better as it's |
40 |
essentially saying you want to explicitly remove it if it's not |
41 |
required; but for normal packages (or multiple packages - it's quicker) |
42 |
I personally prefer deselecting then depcleaning. |
43 |
|
44 |
Just my two small monetary amounts :) |
45 |
-- |
46 |
wraeth <wraeth@×××××××××.au> |