Difference between revisions of "Trinity"

From ArchWiki
Jump to: navigation, search
(update Pkg/AUR templates to reflect new package status)
(Building with Michael's PKGBUILD files: link to developerwiki)
 
(128 intermediate revisions by 11 users not shown)
Line 1: Line 1:
 
[[Category:Desktop environments]]
 
[[Category:Desktop environments]]
{{Article summary start}}
+
[[ja:Trinity]]
{{Article summary text|Trinity is a fork of KDE3 that has been updated to work with current software and libraries. The stable release is 3.5.13. The development release is 14.0.0.}}
+
{{Related articles start}}
{{Article summary heading|Trinity unofficial repositories}}
+
{{Related|Creating packages}}
{{Article summary text|Visit http://archlinux.us.to}}
+
{{Related|pacman tips}}
{{Article summary heading|Related}}
+
{{Related articles end}}
{{Article summary wiki|Creating Packages}}
+
{{Article summary wiki|Custom local repository}}
+
{{Article summary wiki|pacman Tips}}
+
{{Article summary end}}
+
  
The [http://trinitydesktop.org/ 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.  
+
{{Note|Currently the base Trinity packages can be built and installed on Arch using the PKGBUILD files on https://github.com/michael-manley/Trinity_ArchLinux_PKGBUILD. Most components seem to work fine except arts is a bit bugged (least on VMWare) but is a work in progress. Binary packages are available for x86_64 at the moment but will provide i686 as built (See [[Unofficial user repositories#trinity]]). You are all welcome to improve the PKGBUILD files.}}
  
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.  
+
{{Note|Michael's PKGBUILD files were added 2016 March 23, after a long time without any Trinity package repository being available.  They seem to build successfully on a system with the {{Grp|plasma}} package group installed, despite the warning below about building without [[KDE4]] being present. Michael's PKGBUILD files include the ten "required" Trinity core packages described in [https://wiki.trinitydesktop.org/How_to_Build_TDE_Core_Modules#Suggested_Build_Order How_to_Build_TDE_Core_Modules#Suggested_Build_Order], and also tdeaccessibility, tdebindings, and tdeutils.  Please contribute additional Trinity core package PKGBUILD files if you are able.  Also note, these Trinity applications and applets can be run just fine under other Desktop Environments, including KDE Plasma5.}}
  
The current stable release of TDE (3.5.13) was released Nov 1st 2011. A software release update (SRU) for 3.5.13 is planned in late 2012. Current development is on 14.0.0. Both 3.5.13(sru) and 14.0.0 build on Arch with all current libraries. The old stable 3.5.12 release was packaged as an updated kdemod3.
+
The [http://trinitydesktop.org/ Trinity Desktop Environment] (TDE) project is a feature rich desktop environment for Unix-like operating systems with a primary goal of retaining the overall KDE 3.5 computing style. TDE is a fast, stable and mature desktop for Linux.
{{Note|Backwards compatibility with 3.5.X was dropped in 14.0.0 to allow install of TDE/TQt without conflict with KDE4/Qt4.}}
+
  
==The difference between 3.5.13 and 14.0.0==
+
== About TDE ==
 +
The current stable release of TDE (14.0.3) was released 2016 February 28. Current development is on 14.1.0.
  
The versioning change between 3.5.13 and 14.0.0 signifies that backwards compatibility with 3.5.X has been dropped to allow TDE/TQt to install along side KDE4/Qt4 without conflict. 14.0.0 will continue to rely on HAL, but subsequent releases will do away with that dependency. 14.0.0 contains the first prototype of media:/ kioslave as a replacement for HAL. 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.
+
Trinity is an independent fork of KDE 3.5 using a separate developer community. Continued development by the Trinity Project has polished off many rough edges that were present in the final release of KDE 3.5.10. Many new and useful features have been added to keep the environment up-to-date.  
  
Currently the remaining TQt name changes are being implemented after which a tentative code 'freeze' is anticipated to allow user testing and bug identification. 14.0.0 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. All in all, the desktop functions beautifully on current graphics libs, systemd-tools, libusbx, udisk2 and other newly implemented hardware paradigms.
+
R14 is intended to be a true TDE release with all branding, artwork, and graphics changed and updated for this project rather than using holdover KDE3 stock images. The significant improvements and changes to the R14 codebase have been backported to 3.5.13-sru. The desktop functions on current graphics libs, systemd, libusbx, udisk2 and other newly implemented hardware paradigms.
  
==Installation==
+
== Build from source ==
  
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 [https://wiki.archlinux.org/index.php/User:Maevius maevius].  
+
As of July, 2015, there are no Arch LInux Trinity packages, so you will need to create your own. See [[Creating packages]] for more information on how to create Arch packages.
  
For stable 3.5.13-sru snapshots add to your {{ic|/etc/pacman.conf}}:
+
To download the R14 source tarballs, follow the Download Source Tarballs link near the bottom of the [https://www.trinitydesktop.org/releases/R14.0.0/ Trinity R14.0.0 Release] page.
  
[tde3513]
+
The sources are in a git repo. More info on cloning it is at their [https://wiki.trinitydesktop.org/Project_GIT_Information#Using_GIT GIT information] page.
Server = http://archlinux.us.to/3.5.13/$arch
+
  
{{Note|If you have installed packages before 8/18/12, tde-tdeartwork was misssing. Please install that package to insure your selection of screensavers are complete.}}
+
The suggested build order is specified in the [https://wiki.trinitydesktop.org/How_to_Build_TDE How to Build TDE] page.
  
For development 14.0.0 snapshots (expected by 9/1), add to your {{ic|/etc/pacman.conf}}:
+
== Building with Michael's PKGBUILD files ==
  
[tde1400]
+
{{Style|All that matters is the order, the rest is trivial or available from the wiki|section=Trinity Build}}
Server = http://archlinux.us.to/14.0.0/$arch
+
  
Meta package installation for tde is provided under the name {{ic|tde-base}}. Simply install with:
+
{{Note|See [[DeveloperWiki:Building in a Clean Chroot]] to build the packages in a chroot.}}
  
pacman -Syu tde-base
+
[[makepkg|Build]] the packages in the following order, for example:
  
{{Note|On install, you should expect conflicts with tde-sip and tde-sip4-tqt. The TDE packages {{ic|tde-sip}} and {{ic|tde-sip4-tqt}} are direct replacements for the {{ic|sip}} and {{ic|python2-sip}} packages. They simply contain additional extensions for TDE. If you encounter these conflicts, the recommended install is:
+
{{bc|1=#!/bin/sh
 +
git clone <nowiki>https://github.com/michael-manley/Trinity_ArchLinux_PKGBUILD.git</nowiki> trinity
 +
cd trinity/R14.0.3
 +
dir=$PWD
  
pacman -Rdd sip python2-sip
+
for pkg in tqt3 tqtinterface arts dbus-tqt dbus-1-tqt tqca-tls libart-lgpl avahi-tqt tdelibs tdebase tdebindings tdeaccessibility tdeutils; do
pacman -Syu tde-base
+
  cd "$dir"/tde-"$pkg"
 +
  makepkg -Lsci
 +
done
 
}}
 
}}
  
{{Warning|If attempting to install 3.5.13 along side KDE4 you will experience conflicts with {{ic|libart-lgpl}} and {{ic|kdebase-workspace}}. The {{ic|libart-lgpl}} packages are equivalent. The {{ic|kdebase-workspace}} conflict is with {{ic|/etc/ksysguarddrc}}. Both are in the process of being eliminated.}}
+
In TDE R14.0.3, the tdebindings package will not build with the current {{Pkg|ruby}} 2.3 package installed on the system, or even with the {{AUR|ruby2.2}} package, despite the [https://wiki.trinitydesktop.org/Release_Notes_For_R14.0.3 R14.0.3 Release Notes] claim to have "Added ruby 2.2 support". In particular {{ic|tdebindings/qtruby/rubylib/qtruby/Qt.cpp}} seems to not be compatible with either package. Remove the ruby package while building tdebindings and re-install afterwards.
  
==Start and configuration==
+
Then also, consider your preference for path ordering, whether {{ic|/opt/trinity/bin}} should come before or after {{ic|/usr/bin}}.  This will give priority to one or the other of the KDE applications available through both Trinity and KDE/Plasma, if KDE/Plasma is also installed. The PATH environment variable may need to be modified in {{ic|~/.bash_profile}} and/or {{ic|/etc/profile.d/trinity.sh}}.
After a successful install of TDE, starting TDE from the command line or configuring {{ic|/etc/inittab}} to launch tdm is straightforward. The init script for the display manager has been renamed from {{ic|kdm}} to {{ic|tdm}} to avoid conflicts.
+
  
===Configure to work with startx===
+
{{Warning|If Trinity is installed alongside another Qt-based Desktop Environment, such as [[LXQt]] or [[KDE]], then move, modify, or in some way disable {{ic|/etc/profile.d/tqt3.sh}} and {{ic|/etc/profile.d/trinity.sh}}. Otherwise the alternative Desktop will fail horribly when the "QT" and "XDG" environment variables are redefined in these files!}}
Trinity provides a normal {{ic|starttde}} in {{ic|/opt/trinity/bin}} (symlink provided in 3.5.13). The easiest way to start Trinity is to simply add {{ic|/opt/trinity/starttde}} entry at the end of {{ic|~/.xinitrc}}. If you do not presently have {{ic|~/.xinitrc}}, then simply create it with the following entry:
+
  
{{hc|~/.xinitrc|exec /opt/trinity/bin/starttde}}
+
Both these files can be selectively enabled by wrapping their content with:
  
Then from the command line, just type {{ic|startx}}.
+
{{bc|1=
 
+
if ps -C starttde,starttrinity &>/dev/null ;then
===Configure with kdm greeter===
+
...
Trinity provides a great looking tdm graphical interface. The {{ic|tde-tdebase}} PKGBUILD has been updated to install the {{ic|trinity.desktop}} file in {{ic|/etc/X11/sessions}}. In order to automatically lauch {{ic|tdm}} on boot, edit {{ic|/etc/inittab}} and change the runlevel 5 x startup to:
+
fi
 
+
x:5:respawn:/opt/trinity/bin/tdm -nodaemon
+
 
+
If you modified inittab in runlevel 3, you can use {{ic|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.
+
 
+
==Build from source==
+
 
+
=== PKGBUILDs - current git code ===
+
 
+
For a snapshot of PKGBUILD sources for building against the current GIT tree, see [http://www.3111skyline.com/dl/dt/tde/src R14] and [http://www.3111skyline.com/dl/dt/tde/src3513 3.5.13-sru]. Be sure to read  the [http://www.3111skyline.com/dl/dt/tde/src/README-building.txt README-building.txt].
+
 
+
{{Note|Final PKGBUILD source files will be moved to the tdepackaging GIT tree after 14.0.0 is released.}}
+
 
+
===Build order===
+
The required build order is specified in the [http://www.trinitydesktop.org/wiki/bin/view/Developers/HowToBuild Trinity-HowToBuild]. After building {{ic|tdebase}}, you can start the desktop.
+
{{Warning|Trinity on Arch must be built in a clean environment without [[KDE|KDE4]] present. }}
+
Set up your chroot for building by referencing [[DeveloperWiki:Building in a Clean Chroot]]. Make sure you configure your {{ic|local}} repository in {{ic|$CHROOT/root/repo}} and add each package built to the repository as outlined in the [[DeveloperWiki]].
+
 
+
{{hc|Example|
+
# mkarchroot -u $CHROOT/root
+
# makechrootpkg -c -r $CHROOT
+
# makechrootpkg -r $CHROOT   
+
 
}}
 
}}
Which means respectively:
 
# update the chroot
 
# build first package with the -c option
 
# build remaining packages without update }}
 
  
==Development 14.0.0 status==
+
== Start and configuration ==
  
The following packages have been successfully built from the TDE GIT tree for the upcoming release.
+
After a successful install of TDE, the tdm desktop manager can be used to start TDE (and all other desktops) in the same manner kdm is used to start KDE Plasma. The init script for the display manager has been renamed from {{ic|kdm}} to {{ic|tdm}} to avoid conflicts. TDE includes a tdm.service file allowing systemd to start tdm at boot. TDE can also be started from the command line by including the path to starttde in your ~/.xinitrc. Either way launching tdm or TDE is straightforward.  
  
===Required AUR packages===
+
=== Enable tdm.service in systemd to start tdm at boot ===
  
  {{AUR|hal}}
+
If systemd is configured to boot the default {{ic|multi-user.target}} (default), all that is required is to configure tdm to start at boot is to [[enable]] {{ic|tdm.service}}.
  {{AUR|hal-info}}
+
  {{Pkg|libutempter}}
+
  {{AUR|wv2}}
+
  
===Complete packages - 14.0.0 and 3.5.13-sru===
+
If you encounter any problem, the {{ic|default.target}} may have manually configured. See [[Display manager#Loading the display manager]] for resolution.
  
  tde-abakus
+
=== Configure to work with startx ===
  tde-amarok
+
  tde-arts
+
  tde-avahi-tqt
+
  tde-basket
+
  tde-dbus-1-tqt
+
  tde-dbus-tqt
+
  tde-digikam
+
  tde-dolphin
+
  tde-filelight
+
  tde-gtk-qt-engine
+
  tde-gwenview
+
  tde-k3b
+
  tde-k9copy
+
  tde-katapult
+
  tde-kaffeine
+
  tde-kbarcode
+
  tde-kbookreader
+
  tde-kdiff3
+
  tde-kdirstat
+
  tde-kgtk-qt3
+
  tde-kima
+
  tde-kio-locate
+
  tde-kipi-plugins
+
  tde-kmplayer
+
  tde-knemo
+
  tde-knetload
+
  tde-knetstats
+
  tde-knutclient
+
  tde-koffice
+
  tde-konversation
+
  tde-kpowersave
+
  tde-krename
+
  tde-krusader
+
  tde-ksplash-engine-moodin
+
  tde-libart-lgpl
+
  tde-libcaldav
+
  tde-libcarddav
+
  tde-libkdcraw
+
  tde-libkexiv2
+
  tde-libkipi
+
  tde-libksquirrel
+
  tde-python-tqt
+
  tde-rosegarden
+
  tde-sip
+
  tde-sip4-tqt
+
  tde-soundkonverter
+
  tde-tde-style-qtcurve
+
  tde-tdeaccessibility
+
  tde-tdeaddons
+
  tde-tdeadmin
+
  tde-tdeartwork
+
  tde-tdebase
+
  tde-tdeedu
+
  tde-tdegames
+
  tde-tdegraphics
+
  tde-tdelibs
+
  tde-tdemultimedia
+
  tde-tdenetwork
+
  tde-tdepim
+
  tde-tdesdk
+
  tde-tdesvn
+
  tde-tdetoys
+
  tde-tdeutils
+
  tde-tdevelop
+
  tde-tdewebdev
+
  tde-tqca-tls
+
  tde-tqt3
+
  tde-tqtinterface
+
  tde-twin-style-crystal
+
  tde-wlassistant
+
  tde-yakuake
+
  
===TDE GIT application in need of packaging/updating===
+
Trinity provides a normal {{ic|starttde}}. If you've followed the Arch packaging guidelines, it will be in {{ic|/usr/bin}}. The easiest way to start Trinity is to simply add {{ic|starttde}} at the end of {{ic|~/.xinitrc}}. If you do not presently have {{ic|~/.xinitrc}}, then simply copy it from {{ic|/etc/skel}} or create it with the following entry:
  
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.
+
{{hc|~/.xinitrc|exec starttde}}
  
  adept
+
Then from the command line, just type {{ic|startx}}. More about [[xinitrc]].
  bibletime
+
  compizconfig-backend-kconfig
+
  desktop-effects-tde
+
  filelight-l10n
+
  fusion-icon
+
  kaffeine-mozilla
+
  kbfx
+
  kchmviewer
+
  kcmautostart
+
  kcpuload
+
  kdbusnotification
+
  kdpkg
+
  keep
+
  kerry
+
  kile
+
  kio-apt
+
  kio-umountwrapper
+
  kiosktool
+
  kmyfirewall
+
  kmymoney
+
  knetworkmanager8
+
  knetworkmanager9
+
  knights
+
  knowit
+
  kopete-otr
+
  kpicosim
+
  kpilot
+
  kpowersave-nohal
+
  kradio
+
  kstreamripper
+
  ksystemlog
+
  ktechlab
+
  ktorrent
+
  kvirc
+
  kvkbd
+
  kvpnc
+
  piklab
+
  potracegui
+
  qt4-tqt-theme-engine
+
  smartcardauth
+
  smb4k
+
  soundkonverter
+
  tde-guidance
+
  tde-style-lipstik
+
  tde-systemsettings
+
  tdesudo
+
  tdesvn
+
  tellico
+
  libtqt-perl
+
  pytdeextensions
+
  python-trinity
+
  tdebindings
+
  tdesdk
+
  
==Known issues==
+
== Refusing to give up the Trinity "Kicker" panel ==
  
===Issues for 3.5.13-sru===
+
If you simply must have the Trinity "kicker" Desktop Panel and Applets while running Plasma5 or some other Desktop Environment, create this script and activate it. For Plasma5, use "System Settings -> Startup and Shutdown -> Autostart -> Add Script".
  
The following are issues that are specific to the 3.5.13-sru release:
+
{{hc|panelstart|
 
+
#!/bin/bash
KHelpCenter documentation from packages built with autotools are installed in {{ic|/opt/trinity/share/doc/HTML}} while documentation from CMake packages are installed in {{ic|/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 {{ic|/opt/trinity/share/doc/tde/HTML}}. This also insures a future {{ic|/usr}} install will not conflict with any [[KDE]] help files. As a workaround in the mean time, after installing 3.5.13-sru:
+
/opt/trinity/bin/tdeinit
 
+
/opt/trinity/bin/kicker
cd /opt/trinity/share/doc/kde/HTML/en
+
/opt/trinity/bin/tdebuildsycoca --noincremental
for i in ../../../HTML/en/*/; do ln -s $i; done
+
}}
 
+
and
{{Note|Substitute your language for {{ic|en}}}}
+
{{bc|
 
+
# chmod 755 panelstart
Package {{ic|tde-tdesvn}} for x86_64 had been built with libpath {{ic|/opt/trinity/lib64}} and {{ic|/opt/trinity/lib64/trinity}} , but there was no any records in libpath about them. Then, starting {{ic|kdesvn}} you get error ''{{ic|libkdesvnpart.la not found in paths}}''. As a workaround you may copy/symlink libraries from {{ic|/opt/trinity/lib64}} and {{ic|/opt/trinity/lib64/trinity}} into {{ic|/opt/trinity/lib}} and {{ic|/opt/trinity/lib/trinity}} respectively or try to create libpath record and {{ic|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 [http://trinitydesktop.org/contributors.php the list of contributors] is growing. Anyone wanting to help can simply join in. Please email Calvin Morrison.
+
 
+
===Archlinux===
+
* Calvin Morrison: Trinity and Arch a/k/a "mutantturkey", PKGBUILD development and collaboration.
+
* Kaiting Chen: Arch Linux - server space for testing Trinity binaries in the past.
+
* Albert Vaca: kdemod3 updated based on Trinity Stable codebase.
+
* David C. Rankin: 14.0.0 (3.5.13-sru) Development and Packaging
+
 
+
===Developers===
+
* Timothy Pearson: Project administrator, primary developer, build farm administrator, Debian/Ubuntu packaging maintainer.
+
* Darrell Anderson: 3.5.13 -> 14.0.0 Lead coordinator for development and rebranding. Build system preprocessor improvements.
+
* Sl&aacute;vek Banko: 3.5.13-sru developer, GIT maintainer, R14 backport selection and integration.
+
* Serghei Amelian: General functionality enhancements, CMake build system developer/maintainer.
+
* "Woodsman": Vanilla build testing, Slackware packaging maintainer.
+
* Francois Andriot: Developer, Redhat/Fedora packaging maintainer.
+
* David Rankin: 3.5.13-sru and R14 development, upstream library change implementation, graphics, Arch Packaging.
+
  
===Content Distribution===
+
Yum!
* University of Idaho: Mirror 1 [United States]
+
* Jens Dunzweiler: Mirror 2 [Germany]
+
* Inga Muste: Kubuntu LiveCD mirror
+
  
===Web Team===
+
== See also ==
*Calvin Morrison: Website design.
+
*Inga Muste: Website design.
+
  
==See also==
+
* Getting Involved with Trinity Development [https://trinitydesktop.org/helpwanted.php https://trinitydesktop.org/helpwanted.php]
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:
+
 
* Main Project Site: [http://trinitydesktop.org/ http://trinitydesktop.org]
 
* Main Project Site: [http://trinitydesktop.org/ http://trinitydesktop.org]
 
* TDE GIT Repository: [http://git.trinitydesktop.org/cgit/ http://git.trinitydesktop.org/cgit/]
 
* TDE GIT Repository: [http://git.trinitydesktop.org/cgit/ http://git.trinitydesktop.org/cgit/]
* TDE GIT SCM Manager: [http://scm.trinitydesktop.org/scm/ http://scm.trinitydesktop.org/scm/]
 
 
* Bug Reporting: [http://bugs.trinitydesktop.org/ http://bugs.trinitydesktop.org]
 
* Bug Reporting: [http://bugs.trinitydesktop.org/ http://bugs.trinitydesktop.org]
 
* Mailing Lists: [http://trinitydesktop.org/mailinglist.php http://trinitydesktop.org/mailinglist.php]
 
* Mailing Lists: [http://trinitydesktop.org/mailinglist.php http://trinitydesktop.org/mailinglist.php]
* Developers Web: [http://trinitydesktop.org/wiki/bin/view/Developers/WebHome http://trinitydesktop.org/wiki/bin/view/Developers/WebHome]
+
* Developers Web: [https://wiki.trinitydesktop.org/Category:Developers https://wiki.trinitydesktop.org/Category:Developers]
* Trinity Qt4 Conversion: [http://trinitydesktop.org/wiki/bin/view/Developers/TrinityTQtforQt4Conversion http://trinitydesktop.org/wiki/bin/view/Developers/TrinityTQtforQt4Conversion]
+
* QT and TQT Tutorials and Documentation: [https://wiki.trinitydesktop.org/Category:Developers#Tutorials_and_Documentation_for_QT_and_TQT https://wiki.trinitydesktop.org/Category:Developers#Tutorials_and_Documentation_for_QT_and_TQT]
* How To Build: [http://trinitydesktop.org/wiki/bin/view/Developers/HowToBuild http://trinitydesktop.org/wiki/bin/view/Developers/HowToBuild]
+
* How To Build: [https://wiki.trinitydesktop.org/Category:Developers#Building_and_Distributing_Trinity https://wiki.trinitydesktop.org/Category:Developers#Building_and_Distributing_Trinity]

Latest revision as of 06:20, 29 March 2016

Related articles

Note: Currently the base Trinity packages can be built and installed on Arch using the PKGBUILD files on https://github.com/michael-manley/Trinity_ArchLinux_PKGBUILD. Most components seem to work fine except arts is a bit bugged (least on VMWare) but is a work in progress. Binary packages are available for x86_64 at the moment but will provide i686 as built (See Unofficial user repositories#trinity). You are all welcome to improve the PKGBUILD files.
Note: Michael's PKGBUILD files were added 2016 March 23, after a long time without any Trinity package repository being available. They seem to build successfully on a system with the plasma package group installed, despite the warning below about building without KDE4 being present. Michael's PKGBUILD files include the ten "required" Trinity core packages described in How_to_Build_TDE_Core_Modules#Suggested_Build_Order, and also tdeaccessibility, tdebindings, and tdeutils. Please contribute additional Trinity core package PKGBUILD files if you are able. Also note, these Trinity applications and applets can be run just fine under other Desktop Environments, including KDE Plasma5.

The Trinity Desktop Environment (TDE) project is a feature rich desktop environment for Unix-like operating systems with a primary goal of retaining the overall KDE 3.5 computing style. TDE is a fast, stable and mature desktop for Linux.

About TDE

The current stable release of TDE (14.0.3) was released 2016 February 28. Current development is on 14.1.0.

Trinity is an independent fork of KDE 3.5 using a separate developer community. Continued development by the Trinity Project has polished off many rough edges that were present in the final release of KDE 3.5.10. Many new and useful features have been added to keep the environment up-to-date.

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

Build from source

As of July, 2015, there are no Arch LInux Trinity packages, so you will need to create your own. See Creating packages for more information on how to create Arch packages.

To download the R14 source tarballs, follow the Download Source Tarballs link near the bottom of the Trinity R14.0.0 Release page.

The sources are in a git repo. More info on cloning it is at their GIT information page.

The suggested build order is specified in the How to Build TDE page.

Building with Michael's PKGBUILD files

Tango-edit-clear.pngThis article or section needs language, wiki syntax or style improvements.Tango-edit-clear.png

Reason: All that matters is the order, the rest is trivial or available from the wiki (Discuss in Talk:Trinity#Trinity Build)
Note: See DeveloperWiki:Building in a Clean Chroot to build the packages in a chroot.

Build the packages in the following order, for example:

#!/bin/sh
git clone https://github.com/michael-manley/Trinity_ArchLinux_PKGBUILD.git trinity
cd trinity/R14.0.3
dir=$PWD

for pkg in tqt3 tqtinterface arts dbus-tqt dbus-1-tqt tqca-tls libart-lgpl avahi-tqt tdelibs tdebase tdebindings tdeaccessibility tdeutils; do
  cd "$dir"/tde-"$pkg"
  makepkg -Lsci
done

In TDE R14.0.3, the tdebindings package will not build with the current ruby 2.3 package installed on the system, or even with the ruby2.2AUR package, despite the R14.0.3 Release Notes claim to have "Added ruby 2.2 support". In particular tdebindings/qtruby/rubylib/qtruby/Qt.cpp seems to not be compatible with either package. Remove the ruby package while building tdebindings and re-install afterwards.

Then also, consider your preference for path ordering, whether /opt/trinity/bin should come before or after /usr/bin. This will give priority to one or the other of the KDE applications available through both Trinity and KDE/Plasma, if KDE/Plasma is also installed. The PATH environment variable may need to be modified in ~/.bash_profile and/or /etc/profile.d/trinity.sh.

Warning: If Trinity is installed alongside another Qt-based Desktop Environment, such as LXQt or KDE, then move, modify, or in some way disable /etc/profile.d/tqt3.sh and /etc/profile.d/trinity.sh. Otherwise the alternative Desktop will fail horribly when the "QT" and "XDG" environment variables are redefined in these files!

Both these files can be selectively enabled by wrapping their content with:

if ps -C starttde,starttrinity &>/dev/null ;then
...
fi

Start and configuration

After a successful install of TDE, the tdm desktop manager can be used to start TDE (and all other desktops) in the same manner kdm is used to start KDE Plasma. The init script for the display manager has been renamed from kdm to tdm to avoid conflicts. TDE includes a tdm.service file allowing systemd to start tdm at boot. TDE can also be started from the command line by including the path to starttde in your ~/.xinitrc. Either way launching tdm or TDE is straightforward.

Enable tdm.service in systemd to start tdm at boot

If systemd is configured to boot the default multi-user.target (default), all that is required is to configure tdm to start at boot is to enable tdm.service.

If you encounter any problem, the default.target may have manually configured. See Display manager#Loading the display manager for resolution.

Configure to work with startx

Trinity provides a normal starttde. If you've followed the Arch packaging guidelines, it will be in /usr/bin. The easiest way to start Trinity is to simply add starttde at the end of ~/.xinitrc. If you do not presently have ~/.xinitrc, then simply copy it from /etc/skel or create it with the following entry:

~/.xinitrc
exec starttde

Then from the command line, just type startx. More about xinitrc.

Refusing to give up the Trinity "Kicker" panel

If you simply must have the Trinity "kicker" Desktop Panel and Applets while running Plasma5 or some other Desktop Environment, create this script and activate it. For Plasma5, use "System Settings -> Startup and Shutdown -> Autostart -> Add Script".

panelstart
#!/bin/bash
/opt/trinity/bin/tdeinit
/opt/trinity/bin/kicker
/opt/trinity/bin/tdebuildsycoca --noincremental

and

# chmod 755 panelstart

Yum!

See also