5 Feb
2019
5 Feb
'19
7:46 a.m.
phiebie(a)drei.at wrote:
Maybe (many more). But in the meantime I detected
already one nasty
thing.
TDE-sysguard depends on lm-sensors 3.0.5. But this sensor depends on
KDE-sysguard 4.14.5 and the latter removes KDE-sysguard 3.5.10. But the
rest of KDE 3.5.10 does not like the new sysguard at all, so crashes.
What to do with that dependencies?
I don't see any dependency on lm-sensors in
apt-cache show ksysguard-trinity
...
...
Depends: libacl1 (>= 2.2.51-8), libattr1 (>= 1:2.4.46-8), libc6 (>= 2.14),
libfontconfig1 (>= 2.11), libfreetype6 (>= 2.2.1), libgcc1 (>= 1:3.0),
libice6 (>= 1:1.0.0), libidn11 (>= 1.13), libr0, libsm6, libstdc++6 (>= 5),
libtqt3-mt (>= 4:14.1.0), libtqtinterface, libx11-6, libxcomposite1 (>=
1:0.3-1), libxext6, libxrender1, tdelibs14-trinity, zlib1g (>= 1:1.1.4),
ksysguardd-trinity
Overlaps, I don't think so. I remember vaguely,
that Slavek once said,
that he carefully avoided to use the same names for TDE as they were in
KDE.
Please write KDE3 not just KDE. And no, no everything is renamed and will be
renamed soon. It has been done for core packages, but many other still
use "k"
Last but not least:
When I moved to TDE from KDE3 I did it first in a virtual machine to see
what needs to be fixed. I took some notes and then did it on the desktop.
Few things were to be done like settings and PIM settings, but in general it
was work for perhaps half a day all together.
and it payed off. I do not understand your frustration, honestly!