Package: kdelibs-bin
--- Please enter the report below this line. ---
Hi,
I also want to use several old KDE programmes, hence I suggest an
alternative solution to consider:
You could, if already present, divert those two OLD files to
non-conflicting names, like "/usr/bin/kmailservice3" and
"/usr/bin/ktelnetservice3". A script would have to test for the old
"kdelibs4c2a" package's existence, and for the diversion to be already
in place, in order to make sure to not divert previous versions of the
NEW package's files, which can simply be replaced by a more recent
version.
In pseudo-code:
if package_installed(kdelibs4c2a)
then {
if not_already_diverted(ktelnetservice)
then {
rename(ktelnetservice->ktelnetservice3)
}
if not_already_diverted(kmailservice)
then {
rename(kmailservice->kmailservice3)
}
}
continue_normally
This should not have any impact on leftover old software, which,
if it uses those files at all, would simply call the new versions
instead. I think the probability of failure due to the new files
reacting differently is very low in this special case.
Installing old KDE-3-software containing the same files AFTER
the upgrade of KDE would let the package management refuse to overwrite
the then already present NEW file versions, so even if "oldstable" is
still in "sources.list", there is no real problem.
Having moved pre-installed files out of the way, there is no need to
introduce an otherwise unnecessary conflict.
Regards, Christoph Franzen
Attachment:
signature.asc
Description: PGP signature