On 01/02/2016 08:33 AM, Xen wrote:
It is pretty standard procedure.
The .kde4 directory shouldn't get in the way of .kde5 (if that is what Leap uses) but it would have on any Ubuntu system, (or Kubuntu) where kde4 was installed in .kde, as well as kde5 for later versions (was also installed there).
Typically there is no way to know unless you know everything about everything about everything impossible to know,
whether or not there is going to be some conflict particularly in the .config directory, but .local could also have an impact.
Ideally this should not happen: a new version of KDE should work in a different directory (.kde5) and it should not interfere with .kde4.
So what this means is, apparently something was using .local, but .cache could also be a culprit.
So the answer to your question is: yes, you need to at least delete .cache, and possibly .local and .config.
It's unfortunate that it works this way because it also means keeping two versions of e.g. KDE together on the same home volume is difficult.
Then, having a shared home between many (or more) (or multiple) installations of Linux is very difficult.
This would require one of the following:
- use only a shared folder for non-dot files - hand pick the hidden files you want to share (such as .thunderbird) and put them on an overlay filesystem that is overlayed on top of the "real" "current" home directory.
I was experimenting with this on Kubuntu but then I ran into trouble with OpenSUSE because the "aufs" filesystem I used on *Ubuntu is not available on OpenSUSE.
My idea was:
- put the non dot files on a volume shared between distributions - create on each distribution an overlay between that shared volume, and the root volume for that distribution, where the shared volume would take precedence, but all dot files created during installation (on the root fs) would be maintained on the root fs.
In this way each distribution could create its own .config .local etc. hierarchies during installation, but they would get masked by the /SHARED/ versions of those files (and directories) if and only if the shared volume did have a version of it.
You could then simply turn any .file into a shared file simply by copying it to the shared folder. The shared volume.*
But that aside.
Aufs was not available on OpenSUSE and it increases the maintenance cost of a non-standard system, so I haven't used it anymore.
Regards.
I thought about doing the same thing basically, but then I saw how much work it was going to be just to make my system able to run in both. So decided against it and figured it would be just as much work to just make sure I can get KDE 5 to run smoothly. -- George Box #1: 13.2 | KDE 4.14 | AMD Phenom IIX4 | 64 | 16GB Box #2: 13.1 | KDE 4.12 | AMD Athlon X3 | 64 | 4GB Laptop #1: 13.1 | KDE 4.12 | Core i7-2620M | 64 | 8GB Laptop #2: 42.1 | KDE Plasma 5 | Core i7-4710HQ | 64 | 16GB -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org