Ciaran McCreesh wrote:
Because, when I installed gcc 4.3, I could then unmerge the old gcc.
That's why I didn't complain about that. With python, we still have to
have the current version plus the new version which is not being used at
On Fri, 19 Mar 2010 04:23:31 -0500
It's being installed because it's a dependency of something you use.
Replace Python with any other library and we wouldn't be having this
OK. Right now, as you type this, what package depends on python-3
and won't work with python-2? Anything at all? If it is nothing,
then why install it?
And that's where you're making the mistake: you're treating Python as
being different from every other package.
In every other case, you want things to be using the newest version of a
slotted package where possible. Why aren't you complaining that you were
forced to install gcc 4.3 and 4.1 when 3.4 worked just fine?
Am I not correct in that? If the new python is installed, what exactly
is going to use it? I used the new gcc. It worked fine. I unmerged
the old one with no wasted space and one less package installed. This
doesn't appear to be the case with python-3 tho. It's going to be
installed and just sit there like a rock.