Indiana Non-Profit Information Technology Organization, Inc. Let's Encrypt Certificate Expires in 26 days and 9 hours

 
 Navigation 
Home
About Us
Location
Bylaws
Services
Projects
FAQ's
Needs
News
Thanks
Personnel
Videos
How To
Links
 
 Contacts 
Phone:
(574) 780 - 4877
 
E-Mail:
contact@inpito.org
   
 Powered By 
Slackware,
 
Free DNS,
 
An Old Laptop,
 
& Let's Encrypt
 
 
Donate
 

Trinity Desktop for Slackware(64) 14.2 & 14.1 + Multilib System!

Please send emails concerning our Trinity build to trinity@inpito.org
Please do not send emails to contact@inpito.org unless you are interested in joining the I.N.P.I.T.O.
Please consider donating as we have done over $657,280+ dollars worth of free I.T. and have only recieved $1120 dollars in donations.

 The Trinity Desktop for Slackware(64) 14.2 & 14.1 + Multilib System 

Greetings to those of you who like Slackware, like me, but prefer the Trinity desktop more so then the Plasma5 or KDE4 desktop, I have completed my personal build script, for the Trinity desktop to compile and installation, on Slackware 14.2 - using - Trinity r14.0.3. The source code was downloaded from the Trinity Source Code page. I have however modified them to suite my needs. I hope you like it. I make no guarantees about this software of any kind!

The build script compiles the Trinity desktop as the native desktop for Slackware(64) 14.2, and installs it in the /usr tree of Slackware(64). The entire build scripts with source code can be downloaded as a single package here. I've recently compiled both 32 & 64 bit packages, on a clean Slackware(64) VM install, and am providing them here as single package downloads.
 
trinity-r14.0.3-inpito.tar.bz2 : 335.2 MB : md5sum e2c6e2b619b76caa4bc6a37ff29106df - Source & Build Scripts
 
tde-r14.0.3-i486-inpito.tar.bz2 : 653.9 MB : md5sum 79e059e75bf88ed663485b5663049b31 - 32-Bit Packages
 
tde-r14.0.3-x86_64-inpito.tar.bz2 : 589.8 MB : md5sum 7e1f7d8552c3ef7d7d8a13dea6e5742c - 64-Bit Packages
 

The build script compiles the Trinity desktop as the native desktop for Slackware(64) 14.1, and installs it in the /usr tree of Slackware(64). The entire build scripts with source code can be downloaded as a single package here. I've compiled both 32 & 64 bit packages, on a clean Slackware(64) install, and am providing them here as single package downloads.
 
trinity-r14.0.1-inpito.tar.bz2 : 381.9 MB : md5sum 980bbb3014962d41806e2bb489a8c854 - Source & Build Scripts
 
tde-r14.0.1-i486-inpito.tar.bz2 : 651.8 MB : md5sum 7cc2f22a92a3a8a66ee527a55dfe40b2 - 32-Bit Packages
 
tde-r14.0.1-x86_64-inpito.tar.bz2 : 578.5 MB : md5sum 5c2a9b879e08de5eaf72297f978e36e8 - 64-Bit Packages
 

Thank you to all the other Trinity Desktop enthusiasts who have help me get this far!

 
 How to compile and/or install 

These instructions are distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

1. Download your desired package trinity-r14.0.3-inpito.tar.bz2 or tde-r14.0.3-i486-inpito.tar.bz2 or the tde-r14.0.3-x86_64-inpito.tar.bz2 file, and save it to an install location. "I use a thumb drive, or my NFS server." then extract the Bz2 archive file.  The source and build scripts extracked files are about 335 MB in size, the i486 binaries are about 653 MB in size, and the x86_64 binaries are about 590 MB in size.

# wget http://www.inpito.org/Downloads/trinity-r14.0.3-inpito.tar.bz2
# tar jxvf trinity-r14.0.3-inpito.tar.bz2

or

# wget http://www.inpito.org/Downloads/tde-r14.0.3-i486-inpito.tar.bz2
# tar jxvf tde-r14.0.3-i486-inpito.tar.bz2

or

# wget http://www.inpito.org/Downloads/tde-r14.0.3-x86_64-inpito.tar.bz2
# tar jxvf tde-r14.0.3-x86_64-inpito.tar.bz2

2. Install either Slackware-14.2 or Slackware64-14.2, from a source of your choosing.  I personally download the DVD iso.  However, when installing do "NOT" install any package under the KDE4 selection.  This means when you install Slackware you will have to UNSELECT the "[] KDE QT and K Destop Enviroment for X" during the installation process.  Likewise, choose no desktop which would be "Cancel" when the xwmconfig screen appears, while setting up the operating system.

Note: This may be optional. After I install Slackware, I remove the /usr/local directory and replace it with a soft link back the /usr directory.
# rm -R /usr/local
# ln -s /usr /usr/local

However; if you've already installed additional packages to your /usr/local directory, you'll need to decide whether to proceed with this option.

3. Optionally; only for 64-Bit systems. Once the Slackware operating system is up and running, install Alien Bob's multilib system packages for Slackware64 14.2, then for good measure reboot the system. ... Thank You Alien Bob

4. Go to the location of the tde-r14.0.3-(arch)-inpito, directory depending on your package download, and for the build script issue the command.

# ./trinity.compile.sh

or for binary package installation, at the prompt type

# upgradepkg --reinstall --install-new *.t?z

This compile and/or install takes some time so please be patient. Once the compile and/or installation is complete. at the prompt type.

# xwmconfig

Select the ...

xinitrc.trinity TDE: Trinity Desktop Enviroment

Once selected the program should exit. Then reboot the computer. Once the computer reboots log in and at the prompt type startx and launch the Trinity Desktop.  Please remember there are application that are not included in this build, such as Amrok, and k3b.  Lord willing, I will succeed at including more packages to the compile tree in the future, but for now this is all I got.  If you have any edification or comments for me concerning these scripts, ect ... please contact me at Jerry Nettrouer II <trinity@inpito.org> and not my other inpito.org email accounts.

Note: Please remember this will install Trinity into the native /usr directory structure, not the /opt/trinity directory, what that means is that if you attempt to install binaries from packages built for the /opt/trinity directory don't expect them to work with the inpito build packages.

Finally: I am not above error or mistake, so if you find any errors, or mistake, it would be nice to have some insight into it, and any solution to those errors or mistakes.

 
 
Designed by I.N.P.I.T.O. Team 2012 all rights reserved.