Somewhere out here in the recent past, we have a somewhat similar lengthy thread about all this. One suggestion was to “download xyx, edit files X and Y, and change this config file and and change that file”.
Hmmm. so what happens if an update changes some of that? I also suggested the “sudo -E …” option.
Anyway, I find it a less hassle to just do the “sudo -E …”. and if wanted, create a simple script to execute that is easy enough
( sidenote: retired (now 5 years) software engineer of 40 or so years, who now avoids excessive effort )
I am all for pragmatic solutions, and when I researched that whole topic, of course sudo -E was my first approach; only to find out (after users complained) that there are sudo setups that won’t let you do that.
This is why I came up with that /usr/bin/env thing in myrlyn-sudo to preserve a number of known important environment variables. Obviously I missed one or two that KDE seems to be using. But which ones are that? I’d really like very much to add them for those users who can’t simply use sudo -E.
I once had a boss who said that he preferred lazy engineers since those wouldn’t constantly reinvent the wheel and cost the company a lot of money.
