There is a specific order that the individual Trinity components must be built in to prevent unmet dependency errors during build; the first part of this list is presented below:
   * tqtinterface
   * arts
   * kdelibs
   * kdebase
   * kdebindings

The following build order seems to work well for the remaining core packages:
   * kdeaccessibility
   * kdeutils
   * kdemultimedia
   * kdenetwork
   * kdeadmin
   * kdeartwork
   * kdegames
   * kdetoys
   * kdeedu
   * kdegraphics
   * kdesdk
   * kdevelop
   * kdeaddons
   * kdewebdev
   * kdepim

Certain packages are required as additional prerequisites:
   * libical is a requirement to build kdepim
   * sip, pyqt3, and pykde3 (built and installed in that order) are prerequisites to provide python bindings with kdebindings.

Certain packages are not required but provide additional functionality when building Trinity packages:
   * libcarddav (part of the Trinity Project, kdepim)
   * libcaldav (part of the Trinity Project, kdepim)
   * avahi (dns-sd, DNS service discovery/zeroconf, kdelibs/kdebase)
   * lua
   * hspell (Hebrew spell checking)
   * krb5 (kerberos)
   * OpenEXR Libraries (EXR image format support, several KDE packages)
   * GraphicsMagick (various image filters; e.g. koffice/krita, kdebase)
   * JRE-Java Runtime Engine (kdebindings)
   * JDK-Java Development Kit (kdebindings)
   * PostgreSQL (koffice/kexi)
   * transcode, ffmpeg (k3b ripping)
   * libdvdread, libdvdnav (k3b video ripping)

Certain modules will not build across multiple cores in parallel; i.e. with a gcc -j flag set to anything greater than 1. These packages are:
   * kdelibs
   * kdebindings
   * kdemultimedia
   * kdepim
   * koffice