1 |
Apparently, though unproven, at 16:40 on Tuesday 10 May 2011, Grant Edwards |
2 |
did opine thusly: |
3 |
|
4 |
> I ran emerge --depclean the other day on one of my machines and it |
5 |
> removed Python 2.6. I was using Python 2.6 as my "default" python, |
6 |
> and depclean's removal of it broke a _lot_ of stuff. About a half |
7 |
> day's worth of hassle later I had Python 2.6 re-installed and my |
8 |
> system was again usable. |
9 |
> |
10 |
> In order to avoid the same circus on my other machines, how do I |
11 |
> prevent emerge --depclean from removing Python 2.6? |
12 |
|
13 |
Put that slot in world: |
14 |
|
15 |
=dev-lang/python:2.6 |
16 |
|
17 |
I suppose there are better and more automagically elegant ways of doing it, |
18 |
but this works. |
19 |
|
20 |
I think the issue happens because portage does not take eselect choices into |
21 |
account when building it's dep graph, it only uses the DEPENDS in ebuilds. You |
22 |
likely have nothing left that explicitly uses 2.6 and all the ebuilds depend |
23 |
only on python 2 point something |
24 |
|
25 |
When you finally choose to remove python-2.6, you simply have to emerge -C it |
26 |
and not rely on --depclean |
27 |
|
28 |
|
29 |
-- |
30 |
alan dot mckinnon at gmail dot com |