1 |
On Thu, 06 Nov 2014 16:11:49 +1100, wraeth wrote: |
2 |
|
3 |
> > > For future reference, make sure nothing depends on whatever version |
4 |
> > > of python you want to remove before you remove it. If you don't, |
5 |
> > > it could get very interesting in a really bad way. |
6 |
> > |
7 |
> > The simplest way to do that, with any package you want to remove, is |
8 |
> > to use |
9 |
> > |
10 |
> > emerge --depclean --ask -v cat/pkg |
11 |
> > |
12 |
> > instead of |
13 |
> > |
14 |
> > emerge --unmerge --ask cat/pkg |
15 |
> > |
16 |
> > With depclean, dependencies are checked and the package will only be |
17 |
> > removed if nothing depends on it. Adding the -v shows you what |
18 |
> > depends on it. |
19 |
> |
20 |
> It should also be noted that running --depclean on a specific package |
21 |
> *ONLY* removes that package. After depcleaning a specific package, you |
22 |
> should run --depclean again to remove any dependencies of that removed |
23 |
> package: |
24 |
> |
25 |
> emerge --depclean --ask -v cat/pkg |
26 |
> emerge --depclean --ask |
27 |
> |
28 |
> The alternative (at least for packages not in a selected set) is to |
29 |
> |
30 |
> emerge --deselect cat/pkg |
31 |
> emerge --depclean --ask |
32 |
> |
33 |
> This will, oddly enough, deselect the package from being wanted or |
34 |
> "selected", allowing it to be depcleaned, along with its own |
35 |
> dependencies, if no other packages depend on it. |
36 |
|
37 |
Good point. The advantage of depcleaning a particular package is that if |
38 |
something does depend on it, emerge will tell you what, and you may |
39 |
decide to remove or change flags on the dependant package. With deselect, |
40 |
if the initial package is still wanted, the subsequent depclean will do |
41 |
nothing silently. |
42 |
|
43 |
Horses for courses really, |
44 |
|
45 |
|
46 |
-- |
47 |
Neil Bothwick |
48 |
|
49 |
Therapy is expensive, popping bubble wrap is cheap! You choose. |