Re: Plasma 5: no more KDEHOME?
On Jessie, a "export" in a script within /usr/env would take care of the issue. What about stretch? Would a script called /usr/env/kdedirs.sh, containing: export XDG_DATA_HOME=~/.local.stretch/share export XDG_CONFIG_HOME=~/.config.stretch export XDG_CACHE_HOME=~/.cache.stretch ...would fit the bill? Would that be the proper way to go with stretch? João On Tue, Feb 27, 2018 at 6:23 AM, Christian Hilberg < hilb...@kernelconcepts.de> wrote: > Am Montag, 26. Februar 2018, 14:35:05 CET schrieb Joao Roscoe: > > Nice, good to know. > > > > Now, I suppose that in a few years, We'll be moving forward to a newer > > version of our distro of choice. Then we'll (again) face a transitory > > situation in which users will be able to login to different systems with > > different versions of KDE installed, what could result in some trouble, > due > > to different versions of the desktop environment and applications messing > > around with configuration files. In the past, we dealt with this by > > tweaking kde so that it would use "~/.kde. to store kde > > related data, instead of plainly "~/.kde". So, looking at > > https://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html, > > from now on, I guess I could have the same result by tweaking the systems > > to replace "~/.config" wit "~/.config.". > > Don't forget about (at least, maybe there's more) ~/.cache/ and ~/.local/ > > > Is that right? > > > > Best regards, > > Joao > > > > On Sat, Feb 24, 2018 at 11:42 AM, Sune Vuorela > wrote: > > > On 2018-02-22, Joao Roscoe wrote: > > > > How could I avoid conflicts between different versions of kde from > now > > > > > > on? > > > > > > all kde and qt applications follows the XDG spec for this, and the > > > related set of environment variables. > > > > > > /Sune > > Best, > > Christian > > -- >
Re: Plasma 5: no more KDEHOME?
Am Montag, 26. Februar 2018, 14:35:05 CET schrieb Joao Roscoe: > Nice, good to know. > > Now, I suppose that in a few years, We'll be moving forward to a newer > version of our distro of choice. Then we'll (again) face a transitory > situation in which users will be able to login to different systems with > different versions of KDE installed, what could result in some trouble, due > to different versions of the desktop environment and applications messing > around with configuration files. In the past, we dealt with this by > tweaking kde so that it would use "~/.kde. to store kde > related data, instead of plainly "~/.kde". So, looking at > https://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html, > from now on, I guess I could have the same result by tweaking the systems > to replace "~/.config" wit "~/.config.". Don't forget about (at least, maybe there's more) ~/.cache/ and ~/.local/ > Is that right? > > Best regards, > Joao > > On Sat, Feb 24, 2018 at 11:42 AM, Sune Vuorela wrote: > > On 2018-02-22, Joao Roscoe wrote: > > > How could I avoid conflicts between different versions of kde from now > > > > on? > > > > all kde and qt applications follows the XDG spec for this, and the > > related set of environment variables. > > > > /Sune Best, Christian -- signature.asc Description: This is a digitally signed message part.
Re: Plasma 5: no more KDEHOME?
Nice, good to know. Now, I suppose that in a few years, We'll be moving forward to a newer version of our distro of choice. Then we'll (again) face a transitory situation in which users will be able to login to different systems with different versions of KDE installed, what could result in some trouble, due to different versions of the desktop environment and applications messing around with configuration files. In the past, we dealt with this by tweaking kde so that it would use "~/.kde. to store kde related data, instead of plainly "~/.kde". So, looking at https://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html, from now on, I guess I could have the same result by tweaking the systems to replace "~/.config" wit "~/.config.". Is that right? Best regards, Joao On Sat, Feb 24, 2018 at 11:42 AM, Sune Vuorela wrote: > On 2018-02-22, Joao Roscoe wrote: > > How could I avoid conflicts between different versions of kde from now > on? > > all kde and qt applications follows the XDG spec for this, and the > related set of environment variables. > > /Sune > >
Re: Plasma 5: no more KDEHOME?
On 2018-02-22, Joao Roscoe wrote: > How could I avoid conflicts between different versions of kde from now on? all kde and qt applications follows the XDG spec for this, and the related set of environment variables. /Sune
Plasma 5: no more KDEHOME?
Dear Srs, In my environment, home dirs are mounted via NFS, so users will be able to login to several different workstations and always get their stuff transparently. However, sometimes, a user would login to a workstation which had a different version of kde installed (oldstable system, instead of stable one), and in the past this led to several weird problems due to different KDE versions messing around with files in $KDEHOME. To solve this issue, I used to set KDEHOME (system wide) to something like ~/.kde.jessie or ~/.kde.wheezy (instead of default ~/.kde) with an export within /usr/env. However, I have just finished installing my first stretch desktop, and I discovered that all this is plain old stuff with Plasma 5, which doesn't use KDEHOME anymore. How could I avoid conflicts between different versions of kde from now on? Best regards
