1 |
Ciaran McCreesh wrote: |
2 |
> On Fri, 19 Mar 2010 04:23:31 -0500 |
3 |
> Dale<rdalek1967@×××××.com> wrote: |
4 |
> |
5 |
>>> It's being installed because it's a dependency of something you use. |
6 |
>>> |
7 |
>>> Replace Python with any other library and we wouldn't be having this |
8 |
>>> discussion. |
9 |
>>> |
10 |
>> OK. Right now, as you type this, what package depends on python-3 |
11 |
>> and won't work with python-2? Anything at all? If it is nothing, |
12 |
>> then why install it? |
13 |
>> |
14 |
> And that's where you're making the mistake: you're treating Python as |
15 |
> being different from every other package. |
16 |
> |
17 |
> In every other case, you want things to be using the newest version of a |
18 |
> slotted package where possible. Why aren't you complaining that you were |
19 |
> forced to install gcc 4.3 and 4.1 when 3.4 worked just fine? |
20 |
> |
21 |
> |
22 |
Because, when I installed gcc 4.3, I could then unmerge the old gcc. |
23 |
That's why I didn't complain about that. With python, we still have to |
24 |
have the current version plus the new version which is not being used at |
25 |
all. |
26 |
|
27 |
Am I not correct in that? If the new python is installed, what exactly |
28 |
is going to use it? I used the new gcc. It worked fine. I unmerged |
29 |
the old one with no wasted space and one less package installed. This |
30 |
doesn't appear to be the case with python-3 tho. It's going to be |
31 |
installed and just sit there like a rock. |
32 |
|
33 |
Dale |
34 |
|
35 |
:-) :-) |