On Tue, 27 Jul 2021 09:43:00 -0700
"Alec Destry" <xode(a)techccu.com> wrote:
----- Original Message -----
From: "Dr. Nikolaus Klepp" <office(a)klepp.biz>
To: <devels(a)trinitydesktop.org>
Sent: Tuesday, July 27, 2021 2:52 AM
Subject: [tde-devels] Re: Status of TDE ARK timestamp for files in ZIP
archive.
Anno domini 2021 Tue, 27 Jul 01:16:01 -0700
Alec Destry scripsit:
[...]
"ark-trinity 4:14.1.0~s211-0debian11.0.0+10~a"
--> This suggests you're using a KDE4 version of ARK which doesn't have
that
problem. Unfortunately, KDE4 ARK doesn't work well with a KDE3.5 GUI and
a
KDE4/KDE5 GUI is very inflexible and unfriendly.
How does "ark-trinity 4:14.1.0~s211-0debian11.0.0+10~a" relate to
"trinity-ark-14.0.10-1.oss151.x86_64.rpm"?
Definitly no KDE4 :)
14.1.X is the dev version, 14.0.X is the "normal" version.
So, you're stating this problem has been fixed for
trinity-ark-14.0.10-1.oss151.src.rpm and I could download that? Then, I
could look for the corresponding source code for ARK there, replace the part
of the source code in the KDE 3.5 RPM that has the problem with that from
TDE, and compile a KDE3.5 ARK that doesn't have the problem?
The problem has been fixed since at least TDE version 14.0.8, possibly
earlier, so yes, that RPM should contain the fixes if it contains the full
source. Alternatively, you can pull the appropriate source package from
http://tde-mirror.yosemite.net/trinity/releases/R14.0.10/main/core/tdeutils…
or use git to examine only the files that interest you:
https://mirror.git.trinitydesktop.org/gitea/TDE/tdeutils/src/branch/master/…
Whether or not you can extract the relevant patches from the other
changes is another question, but you're welcome to try.
"But this has been fixed ages ago, can't even
remeber that beeing an
issue."
--> It hasn't been fixed for KDE3.5 ARK, which is "supported" by
OpenSuse,
where "supported" means they only make the packages available but don't
keep
them updated.
TDE split from KDE ~ 10 years ago. KDE of OpenSuse does not relate to TDE.
That would be great if that were entirely true. Then, I would be able to
install TDE as a separate available desktop alongside the KDE3.5 desktop I
currently have installed, and continue to use KDE3.5 for the everyday work I
need to use it for, while I working through TDE and getting that set up so
it has the exact same look and feel, and functionality, that I need, as the
KDE3.5 I'm currently using for everyday work. Unfortunately, the TDE
documentation states that TDE can't be installed alongside KDE3.5, since the
two are still enough alike that one would trash the other, unlike, for
example XFCE being installed alongside KDE3.5 where, at the login screen,
you could choose to start XFCE instead of KDE3.5. Or, is that no longer
true, and TDE could be installed alongside the KDE3.5 I'm currently using?
It's complicated. You certainly can't install the standard precompiled
packages using your package manager without the possibility of
accidentally clobbering some things.
You might be able to make it work by compiling TDE from source,
installing to (if necessary) something other than the standard location,
and modifying the starttde and startkde scripts to manage PATH and
such so that the directories searched first for components match the
desktop you're using at the time. (This was the approach Gentoo used
to allow KDE3 and KDE4 to be installed side-by-side on the same
machine back in the day.)
You'd also have to back up your user configuration data, because
some of the TDE installation scripts will update the KDE3 data for
TDE's use.
If running both side-by-side sounds like something you really want
to do, I'd try it inside a VM first, or at least install first to a chroot so
that you can check for file clobbers.
You can also use a plain TDE VM or live CD to test to see whether
or not any of the changes made since KDE3 will disrupt your workflow.
Part of the point of TDE has been not to make significant changes to
how the desktop works, though—there are a sprinkling of replacement
graphics, but few other visible changes.
E. Liddell