Greetings! This is a collection of Trinity binary packages for Slackware 13.1. All standard packages are available as well as a few others. Please notice there are debug symbol packages. This is something Slackware packagers normally do not create. All of those packages have "_debug" in the package name. There is no need to download these packages unless asked to help troubleshoot with a backtrace. Just download the normal binary packages. Use "all-no-debug.iso" to download all regular binary packages. Use "all-with-debug.iso" to download all regular binary packages as well as the debug symbol packages. Use wget, kget, or your browser to download individual packages. If any individual packages have file date stamps more recent than the ISO images then that means I have updated the package but not the ISOs. Uploading those ISOs costs bandwidth and I won't be updating them as often as packages. I'm not really equipped for massive amounts of downloads but we'll give this a try. If you find the packages useful, please donate to the Trinity project. No donated funds will come my way, but the donations will provide me warm fuzzy feelings. ======================================= Updates to 3.5.13 packages since initial November release: * Updated the poppler package. I had correctly merged all security patches but I did so with the original stock poppler rather than the patched version. My package was okay and rebuilt for both Qt3 and Qt4, but the package name was incorrect. In future Trinity releases poppler will not need to be recompiled as a new Trinity package will provide the Qt3 support layer to poppler. * Updated the kdepim package. The first package was not built with SASL support, which is needed for secure logins. * Updated the kdemultimedia package. The first package did not build kaudiocreator because the cdda header files are in a subdirectory of /usr/include and without the --with-extra-includes=/usr/include/cdda configure option, the kaudiocreator binary would not build. Fixed a bug with not building MMX support. * Updated the kdenetwork package with wifi support. Traditionally networking support in KDE3 for Slackware was always awful. Please test and provide feedback. * Updated koffice with GraphicsMagick support. * Rebuilt all packages with support packages listed below. * Created debug symbol packages. To help solve bugs, download the appropriate debug symbol packages to create a backtrace. Please save me some bandwidth by downloading the packages only when needed. * Back ported many patches from GIT. (The next release should be great!) * Unless learning about a major bug, this will be the last of my 3.5.13 support. New packages will be from GIT or the next official release. ======================================= Help is needed and appreciated. Subscribe to Trinity user, developer, and announcement lists: http://trinity.pearsoncomputing.net/mailing_lists/. Report Trinity bugs at http://bugs.pearsoncomputing.net. Please create an account at the bugzilla and help make Trinity a great and useful desktop. Report Slackware build script errors, patches, improvements, build notes, packaging problems, etc. at http://humanreadable.nfshost.com/. Thanks! ======================================= These are 32-bit packages, as you can see from the packages names. I don't have a 64-bit operating system installed to build 64-bit packages. I have 64-bit hardware but I'm lazy. I have a 13.37 32-bit virtual system that I might try to build packages, but that is not a high priority for me. ======================================= Trinity Compatibility With KDE4 Trinity is intended to be compatible with KDE4. The best way I find to do that is to disable the KDE4 scripts in /etc/profile.d (chmod -x). The next Trinity release should alleviate that requirement because many of the environment variables will be renamed. Until then please forward better methods for using both Trinity and KDE4. Thanks! ======================================= Trinity Compatibility With KDE3 Some people have asked whether Trinity and KDE3 can be installed together on the same machine. They can be installed together because all Trinity packages install to /opt/trinity. I have not performed any meaningful tests with using both on the same machine. Please provide feedback if you perform such tests. KMail files are compatible between Trinity and KDE3 but using KMail in Trinity means the index files will be recreated. Those index files are not compatible with KDE3. Opening KMail in KDE3 after doing the same in Trinity will result in message boxes. The indexes can be restored back to KDE3 format and there is no damage, but the messages are annoying. This is not a problem if two separate profile directories are used, but then synchronizing mail between the two profiles becomes a challenge. Please read the aaMIGRATING.txt file for details about migrating KDE3 profiles. ======================================= Other notes: All Trinity packages were built to install to /opt/trinity. The startup script is /opt/trinity/bin/startkde (to be renamed starttde next release :)). The file should install as startkde for new installations, but will install as startkde.new if there is an existing startkde. If Trinity fails to start then check the name of the file. I modified the startkde script from the original script provided with Trinity 3.5.13. To compare the differences you'll have to obtain a copy of the Trinity kdebase source files. There is a new rc.4 startup script that supports the Trinity KDM. Although Trinity supports coexisting with KDE4, that is not the case for KDE3. To run Trinity and KDE3 on the same box probably means disabling the executable bit for one of the KDMs. There is a modified xwmconfig to add support for Trinity. Please test and provide feedback. When installed the original stock xwmconfig from Slackware is renamed and not deleted. :) ======================================= The Trinity packages provided here were built in Slackware 13.1. The packages were built with the following support software installed. Several of these support package are now part of the stock Slackware, starting with Slackware 13.0. These support packages are not required to be installed in Slackware 13.1. Building with that support only means the Trinity packages are built with the internal hooks necessary to take advantage of these packages when installed. Therefore none of the Trinity packages should need rebuilding when installing these support packages. The result is a more robust and flexible desktop and easier maintenance for end-users who do not build packages. facile ocaml boost libsndfile ilmbase openexr graphicsmagick graphviz libmp4v2 JRE-Java Runtime Engine JDK-Java Development Kit sip pyqt3 pykde3 ffmpeg lame faac faad2 speex transcode libdvdcss libdvdread libdvdnav libcaldav libcarddav libical ortp wv2 libmpeg2 libdv a52dec xvidcore schroedinger openjpeg x264