Message: previous - next
Month: July 2012

Re: [trinity-devel] Nightlies & migration handling (k->t )

From: Darrell Anderson <humanreadable@...>
Date: Mon, 9 Jul 2012 11:11:54 -0700 (PDT)
> I did a grep -i kdm /etc/trinity/*/* and it came up with one
> file.
> I've attached the following file:
> kubuntu-default-settings-trinity:
> /etc/trinity/tdm/tdmdistrc
> In the error messages I got from KDM before I added symlinks
> kdm->tdm (and moving everything inside one directory), also kdm was
> in the path.

At this point I don't know where the conflict you describe exists. Thus I'm a bit confused --- nothing new there. :-)

Which set of packages are you using?

If you are using GIT sources (R14 Development), then TDE will use tdm and not kdm. The default system config directory will be /etc/trinity/tdm and not /etc/trinity/kdm.

If you are using 3.5.13 or, then kdm is still used and not tdm. Those releases do not know anything about tdm.

With the GIT sources, if both /etc/trinity/tdm and /etc/trinity/kdm exist, then the latter directory is ignored and no longer used. If you are using GIT sources and your system is trying to use kdm rather than tdm, then I lean toward something distro-specific or system-specific causing that to happen. Possibly a system startup script is hard-coded to kdm rather than tdm.

I have been using the GIT sources as my primary desktop for a while now and do not notice any conflicts or migration issues.

Regarding not seeing the migratekde3 script in your packages, the script gets built into my Slackware packages without any build script help. The cmake files automatically add that script to the tdebase package. The installation location of the script should be the same as starttde.

Regarding the potential second script, I'm unsure what we should check or how. I'm open to ideas. :-) I think first we look at migratekde3 doing its job. If you don't have that script in your GIT packages, you can still test by just grabbing the file from the GIT repository. Although the script works quite well in my system, I believe very few others in the project have vigorously tested the script. All testing is appreciated. :-)