I updated svn but have not yet recompiled. I'm getting there.... :)
> > 1. As non-root Trinity seems to completely honor
> $KDEHOME. There is no
> > ~/.kde3 directory created and Trinity uses my existing
> ~/.kde directory.
> >
> > As root Trinity does not fully honor $KDEHOME.
> >
> <snip>
> Quick comment here. The above was very important.
> ;-) Trinity expects to
> see KDEROOTHOME set, not KDEHOME, when run as root.
> Maybe you can help
> here; is this a Debian-only distinction, or do other Linux
> systems also
> use KDEROOTHOME?
I know about the KDEROOTHOME variable. I have not toyed with a sufficient number of distros to provide a full answer. The stock Slackware does NOT set the variable. Certainly I can adjust my local /etc/profile.d variable scripts to set that variable. I will test that.
With that said, I wonder whether a simple check can be added in Trinty to look at $UID when KDEROOTHOME is not set?
> ===========================================================
> >
> > 4. The existing startkde is Debianized and causes
> breakage on Slackware
> > systems. I am submitting a proposed new startkde
> script. The proposed
> > script avoids certain presumptions and adds some tests
> before running
> > various commands. The proposed script also adds
> additional echo messages
> > to help debugging efforts.
>
> Can you attach it please? I would like to look at
> it/get it in SVN ASAP
> as we have already run past the feature freeze and these
> types of major
> changes need to be tested thoroughly prior to release.
Yes. Attached. I was going to attach to the previous message but decided to wait until I updated svn and could review your changes. :)
My proposed script is more robust that previous scripts, including the original kde scripts. Part of my additions I already had in my own modified 3.5.10 script. The script works fine here, but I don't have a Debian install using Trinity to test there.
Attachments: