1 |
Jesús Guerrero wrote: |
2 |
> On Tue, July 28, 2009 09:29, Hanno Böck wrote: |
3 |
>> While I fully understand that people want to deprecate "old cruft", I |
4 |
>> assume this is far too early. (just think back how long it took us to |
5 |
>> deprecate gtk+-1) |
6 |
> |
7 |
> I fully agree with this thought. The qt4 world is simply nowhere near |
8 |
> as complete and usable (nor stable either, which is worse) as the qt3 |
9 |
> one is. |
10 |
> |
11 |
>> I'm still on kde 3 and my previous three attemps to switch to kde 4 all |
12 |
>> ended up in the conclusion that kde 4 is far from being stable yet. It has |
13 |
>> tons of regressions. |
14 |
|
15 |
Please note that you need to make a distinction between Qt4 and KDE4! |
16 |
The KDE team had already decided to move KDE3 to an overlay early next |
17 |
year, with the release of 4.4. We as Qt team are just following suit. |
18 |
It's just that the KDE team hasn't made as public an announcement yet. |
19 |
|
20 |
A KDE 4.3 version is supposed to be marked stable within the next few |
21 |
months, and this then clears the way for KDE3 deprecation. |
22 |
|
23 |
When KDE3 will be removed early 2010, we as Qt team see no need to keep |
24 |
Qt3 around any longer either. We currently have no developers who are |
25 |
interested in maintaining it, and upstream doesn't either. Qt4 really is |
26 |
a major improvement over Qt3, especially where it concerns non-KDE apps. |
27 |
|
28 |
|
29 |
>> The amount of qt3 apps not having a sane or just no qt4 port yet is |
30 |
>> probably enormous. I also maintain such packages. |
31 |
> |
32 |
> [...] k3b, and [...] kaffeine |
33 |
|
34 |
These are KDE apps, so you need to address the KDE team about that, not |
35 |
the Qt team. But I'm assuming that if these have no working KDE4-based |
36 |
version by early next year, that's just too bad. And on the other hand, |
37 |
for those people who still want to use these applications, there will be |
38 |
the overlay. |
39 |
|
40 |
So, there are very few "pure" Qt3 apps, and even fewer that have no Qt4 |
41 |
port yet. The only major project I'm aware of is MythTV. If there are |
42 |
any others please let me know. |
43 |
|
44 |
|
45 |
> The qt3 stuff is stable, this is not another xmms-like thing, it works, |
46 |
> and it doesn't only work, but today it works *far better* than the qt4 |
47 |
> newer alternatives, in most cases anyway. |
48 |
|
49 |
No, Qt4 works far better than Qt3, and has loads more features. Of |
50 |
course, it is up to the application developers how to use this. Do not |
51 |
confuse KDE4 instability with Qt4 instability. If you compare non-KDE |
52 |
Qt3 apps with non-KDE Qt4 apps, the huge improvements should be |
53 |
self-evident. |
54 |
|
55 |
Even so, our main argument is the question of maintenance. We want to |
56 |
stop wasting time on Qt3 related issues, especially as (1) it is no |
57 |
longer maintained upstream, and (2) its main consumer, KDE3, is |
58 |
scheduled for removal from portage. |
59 |
|
60 |
If you feel passionate about Qt3 and want to make the case for keeping |
61 |
it in portage, then step up and become its maintainer. |
62 |
|
63 |
Cheers, |
64 |
Ben |