Fwd: [opensuse] Re: [opensuse-kde3] 13.1 kde3 build is not removing all calls to HAL
-------- Original Message --------
Subject: [opensuse] Re: [opensuse-kde3] 13.1 kde3 build is not removing all
calls to HAL
Date: Sat, 30 Aug 2014 19:38:28 -0500
From: David C. Rankin
NAICT, all KDE3's own virtues remain in the fork, plus the fork gets the fixes required to work with the evolving foundations, such as systemd and the myriad of changes systemd has caused to X.
What changes related to systemd support Trinity has that KDE3 in openSUSE does not?
None -- that is where I'm stuck with Arch. TDE has the same manpower problems we do here. Here is the relevant bug (I filed it) http://bugs.pearsoncomputing.net/show_bug.cgi?id=1998
In fact Ubuntu (for which Trinity is developed) migrated to systemd the last of all major distributions. So Tribnity migrated to systemd after openSUSE's KDE3 did.
If there were advantages to moving to TDE, I'd be the first to say -- Migrate to TDE, but after building TDE for 3 years and running kde3/opensuse for the same time, there just are not any huge driving reasons for changing, and it just complicates application development with the Qt/TQt name changes. T -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
If there were advantages to moving to TDE, I'd be the first to say -- Migrate to TDE, but after building TDE for 3 years and running kde3/opensuse for the same time, there just are not any huge driving reasons for changing, and it just complicates application development with the Qt/TQt name changes.
The main feature of Trinity was that it in theory (in the uncertain future) could allow to compile it with Qt4 via a special compatibility layer. But now Qt4 is outdated, all applications are migrating to Qt5. But the same approach will not work with Qt5 because it lacks the qt3-support libraries that are part of Qt4. It totally lacks the Qt3-compatible APIs. -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On 08/30/2014 09:08 PM, Ilya Chernykh wrote:
If there were advantages to moving to TDE, I'd be the first to say -- Migrate to TDE, but after building TDE for 3 years and running kde3/opensuse for the same time, there just are not any huge driving reasons for changing, and it just complicates application development with the Qt/TQt name changes.
The main feature of Trinity was that it in theory (in the uncertain future) could allow to compile it with Qt4 via a special compatibility layer. But now Qt4 is outdated, all applications are migrating to Qt5.
But the same approach will not work with Qt5 because it lacks the qt3-support libraries that are part of Qt4. It totally lacks the Qt3-compatible APIs.
The unfortunate consequence of that choice was to include that API in TDE requiring ALL components and 3rd party applications to be ported to use the TQt layer (involving significant renaming within each component and application) That is why I will reiterate, the smartest thing kde3/opensuse can do is to continue with the kde3 source and update Qt3 as needed. There are no hurdles to kde3 continuing to function for many opensuse releases to come as long as consolekit provides user-session tracking. All we need to commit to do in the interim is patch the normal breaks as new libraries are released and keep the code building on the latest gcc/glibc/g++. There is nothing that prevents the continued use of qt3 while we look to some industrious individual to attempt a port to qt5 ;-) -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
The unfortunate consequence of that choice was to include that API in TDE requiring ALL components and 3rd party applications to be ported to use the TQt layer (involving significant renaming within each component and application)
Yes. We have a lot of Qt3 software besiders KDE3 proper. It would be incompatible with Trinity.
That is why I will reiterate, the smartest thing kde3/opensuse can do is to continue with the kde3 source and update Qt3 as needed. There are no hurdles to kde3 continuing to function for many opensuse releases to come as long as consolekit provides user-session tracking.
All we need to commit to do in the interim is patch the normal breaks as new libraries are released and keep the code building on the latest gcc/glibc/g++.
...And this actually can be taken from Trinity or any other project, like that of Serghei's if we could not do that ourselves. A problem with Trinity in this respect is that it is Ubuntu-oriented, and Ubuntu usually lacks behind openSUSE in terms of technological innovations (and they have a conflict with Red Hat who is usually innovating the most in technical terms). openSUSE on the other hand strives to be as compatible with Red Hat/Fedora as possible, thus it includes systemd and other Red Hat's innovations.
There is nothing that prevents the continued use of qt3 while we look to some industrious individual to attempt a port to qt5 ;-)
-- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
participants (2)
-
David C. Rankin -
Ilya Chernykh