The current stable release of TDE (3.5.13) was released Nov 1st 2011. A software release update (SRU) for 3.5.13-sru is complete and tarballs are available for download. Current development is on 14.0.0 (R14). R14 is scheduled for release in January 2014. For both 3.5.13(sru) and r14 the goal is to build on Arch with all current libraries. The old stable 3.5.12 release was packaged as an updated kdemod3.

The current stable release of TDE (3.5.13) was released Nov 1st 2011. A software release update (SRU) for 3.5.13-sru is complete and tarballs are available for download. Current development is on 14.0.0 (R14). R14 is scheduled for release in January 2014. For both 3.5.13(sru) and r14 the goal is to build on Arch with all current libraries. The old stable 3.5.12 release was packaged as an updated kdemod3.

{{Note|Backwards compatibility with 3.5.X was dropped in R14 to remove HAL dependency and to allow install of TDE/TQt without conflict with KDE4/Qt4. The 3.5.13-sru branch provides backwards compatibility with 3.5.X}}

{{Note|Backwards compatibility with 3.5.X was dropped in R14 to remove HAL dependency and to allow install of TDE/TQt without conflict with KDE4/Qt4. The 3.5.13-sru branch provides backwards compatibility with 3.5.X}}

+

+

The initial build of R14 without hal dependency is complete. This signifies the first build of TDE R14 for Archlinux systemd environment and without the holdover hal requirement. See the list of completed packages below. The remaining packages are under development.

==The difference between 3.5.13 and R14==

==The difference between 3.5.13 and R14==

Line 117:

Line 119:

The TDE codebase is in extremely good shape. There have been no code related FTBFS encountered. The most time consuming part of updating the TDE PKGBUILDs for current Arch is removing unneeded patches and locating new package names containing dependencies that were in different packages in the past. The following built without issue (tdelibs (without hal) being the most telling bellweather of how the remainder of the build will go)

The TDE codebase is in extremely good shape. There have been no code related FTBFS encountered. The most time consuming part of updating the TDE PKGBUILDs for current Arch is removing unneeded patches and locating new package names containing dependencies that were in different packages in the past. The following built without issue (tdelibs (without hal) being the most telling bellweather of how the remainder of the build will go)

The Trinity Desktop Environment (TDE) project is a computer desktop environment for Unix-like operating systems with a primary goal of retaining the overall KDE 3.5 computing style. The project was founded by and is still led by Timothy Pearson. Timothy is an experienced and skilled software developer and was the KDE 3.x coordinator of previous Kubuntu releases.

The goal of this project is to keep the KDE3.5 computing style alive, as well as polish off any rough edges that were present as of KDE 3.5.10. Along the way, new useful features have be added to keep the environment up-to-date.

The current stable release of TDE (3.5.13) was released Nov 1st 2011. A software release update (SRU) for 3.5.13-sru is complete and tarballs are available for download. Current development is on 14.0.0 (R14). R14 is scheduled for release in January 2014. For both 3.5.13(sru) and r14 the goal is to build on Arch with all current libraries. The old stable 3.5.12 release was packaged as an updated kdemod3.

Note: Backwards compatibility with 3.5.X was dropped in R14 to remove HAL dependency and to allow install of TDE/TQt without conflict with KDE4/Qt4. The 3.5.13-sru branch provides backwards compatibility with 3.5.X

The initial build of R14 without hal dependency is complete. This signifies the first build of TDE R14 for Archlinux systemd environment and without the holdover hal requirement. See the list of completed packages below. The remaining packages are under development.

The difference between 3.5.13 and R14

The versioning change between 3.5.13 and R14 signifies that backwards compatibility with 3.5.X has been dropped eliminating dependency on HAL and to allow TDE/TQt to install along side KDE4/Qt4 without conflict. R14 will may be built with or without (--nohal) HAL but is intended to remove HAL completely. 3.5.13 continues backwards compatibility with KDE 3.5.10 code and provides an alternative choice for those that prefer. The 3.5 13 branch will be maintained for the forseeable future.

R14 will be a true TDE release with all branding, artwork, and graphics changed and updated for this project rather than using the holdover KDE3 stock images. The changes have been backported to 3.5.14-sru. All in all, the desktop functions beautifully on current graphics libs, systemd-tools, libusbx, udisk2 and other newly implemented hardware paradigms.

Installation

Note: As of January 2014, PKGBUILDS are being updated for the recent 3.5.13-sru release and release of R14 expected this month. The following links may or may not work in the interim

Currently development packages for Arch Linux are available for both 3.5.13-sru and 14.0.0. Server space has been graciously provided by maevius.

Meta package installation for tde is provided under the name tde-base. Simply install with:

pacman -Syu tde-base

Note: On install, you should expect conflicts with tde-sip and tde-sip4-tqt. The TDE packages tde-sip and tde-sip4-tqt are direct replacements for the sip and python2-sip packages. They simply contain additional extensions for TDE. If you encounter these conflicts, the recommended install is:

pacman -Rdd sip python2-sip
pacman -Syu tde-base

Warning: If attempting to install 3.5.13 along side KDE4 you will experience conflicts with libart-lgpl and kdebase-workspace. The libart-lgpl packages are equivalent. The kdebase-workspace conflict is with /etc/ksysguarddrc. Both are in the process of being eliminated.

Start and configuration

After a successful install of TDE, starting TDE from the command line or configuring /etc/inittab to launch tdm is straightforward. The init script for the display manager has been renamed from kdm to tdm to avoid conflicts.

Configure to work with startx

Trinity provides a normal starttde in /opt/trinity/bin (symlink provided in 3.5.13). The easiest way to start Trinity is to simply add /opt/trinity/starttde entry at the end of ~/.xinitrc. If you do not presently have ~/.xinitrc, then simply create it with the following entry:

~/.xinitrc

exec /opt/trinity/bin/starttde

Then from the command line, just type startx.

Configure with kdm greeter

Trinity provides a great looking tdm graphical interface. The tde-tdebase PKGBUILD has been updated to install the trinity.desktop file in /etc/X11/sessions. In order to automatically lauch tdm on boot, edit /etc/inittab and change the runlevel 5 x startup to:

x:5:respawn:/opt/trinity/bin/tdm -nodaemon

If you modified inittab in runlevel 3, you can use telinit to initialize the runlevel 5 services from the command line.

If you experiment with other display managers (slim, etc..) please drop a quick howto here.

Required dependencies for full function

Complete packages (current)

The TDE codebase is in extremely good shape. There have been no code related FTBFS encountered. The most time consuming part of updating the TDE PKGBUILDs for current Arch is removing unneeded patches and locating new package names containing dependencies that were in different packages in the past. The following built without issue (tdelibs (without hal) being the most telling bellweather of how the remainder of the build will go)

TDE GIT application in need of packaging/updating

The following is a list of packages that need PKGBUILDs create and/or code fixes to build with current libraries. If you can help with the project and code updates then please join us on the trinity-devel list (trinity-devel@lists.pearsoncomputing.net). Visit http://www.trinitydesktop.org/mailinglist.php for more information.

Known issues

Issues for 3.5.13-sru

The following are issues that are specific to the 3.5.13-sru release:

KHelpCenter documentation from packages built with autotools are installed in /opt/trinity/share/doc/HTML while documentation from CMake packages are installed in /opt/trinity/share/doc/kde/HTML. This means roughly one-half of the help files are missing from the khelpcenter browser. This is currently being fixed in the GIT tree and the next set of packages will have all help documentation in the chosen standard location of /opt/trinity/share/doc/tde/HTML. This also insures a future /usr install will not conflict with any KDE help files. As a workaround in the mean time, after installing 3.5.13-sru:

cd /opt/trinity/share/doc/kde/HTML/en
for i in ../../../HTML/en/*/; do ln -s $i; done

Note: Substitute your language for en

Package tde-tdesvn for x86_64 had been built with libpath /opt/trinity/lib64 and /opt/trinity/lib64/trinity , but there was no any records in libpath about them. Then, starting kdesvn you get error libkdesvnpart.la not found in paths. As a workaround you may copy/symlink libraries from /opt/trinity/lib64 and /opt/trinity/lib64/trinity into /opt/trinity/lib and /opt/trinity/lib/trinity respectively or try to create libpath record and ldconfig after it.

Issues for 14.0.0

None known

Contributors

At present, the Trinity project for Arch Linux is just beginning. Interest in the project and the list of contributors is growing. Anyone wanting to help can simply join in. Please email Calvin Morrison.

Content Distribution

University of Idaho: Mirror 1 [United States]

Jens Dunzweiler: Mirror 2 [Germany]

Inga Muste: Kubuntu LiveCD mirror

Web Team

Calvin Morrison: Website design.

Inga Muste: Website design.

See also

The Trinity site has a number of good resources available. As with any rapidly developing project, the documentation is somewhat sparse, but it does provide a good basic road-map to follow here. The mailing list has approximately the same volume as the arch-user list, so it will not overwhelm your inbox. If you want to help with this project, it is strongly recommended that you also join the trinity-devel mailing list. All of the following links are available from the Trinity project site. A quick list of helpful links to the project follows: