Trinity Desktop for Slackware Update - Binaries for i486 & x86_64
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Trinity Desktop for Slackware Update - Binaries for i486 & x86_64
I recently built i486 and x86_64 - Trinity Desktop - packages for Slackware 14.1 the packages are compiled as the native desktop, and not for the /opt/trinity directory.
If your interested you can download the i486, x86_64, or build script, each as single packages, from my website at this URL http://www.inpito.org/trinity.php later.
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
A warning for inattentive readers who could have already stored some stuff in /usr/local wouldn't hurt.
Last edited by Didier Spaier; 01-08-2016 at 09:56 AM.
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 install additional packages to your /usr/local directory you'll need to decide whether to proceed with this option.
Out of interest, why do you do that and what has it got to do with Trinity install? Or to put it another way, why would this be part of the instructions?
Well here's what I told Michele Calgaro of the Trinity Desktop Project. - Currently I have a Job, Teach A Class, run a Non-Profit, and try to find time to do I.T. projects.
08/28/2015 08:51 AM,: Me
Hey! I recently got my build script completed for the Trinity Desktop on Slackware64 14.1, as the native desktop. If your interested you can download it and find instructions on my website at this URL http://www.inpito.org/trinity.php later.
08/30/2015 02:42 AM: Michele
Great news, thanks. Would you be interested in becoming a maintainer for the Slackware TDE? ... Cheers ... Michele
09/02/2015 07:33 AM: Me
I thank You for the invitation to join the TDE team in an official manner. However; the non-profit I started is currently in a great need of my attention, as I am at this time the only active person involved, as Doyle has currently focused his attention on other matters.
Unfortunately; I can make no stated commitments to the TDE team, at this time. However; even as we speak I have already found the errors with my build scripts to compile TDE-3.5.13.2 on a 32-Bit Slackware system, and hope to upload the edified version to my website soon. Likewise; I have after about 6 attempts and several disconnects, completed downloading a git - commit from August 29th, of 2015 and hope to modify my already existing scripts to work it, or possibly checkout the r14.0.1 head and in time develop it to compile on a Slackware 14.1 system, if time permits.
Once again, I do thank you for the invitation to join, however it would terrify butter to be spread as thin as I am, at this time, but I hope to do what I can, when time permits.
Meanwhile; if you have time, and are not spread too thin, please aid me in beta testing my corn library to help me determine if the random number generator is in fact a true random number generator. - http://www.inpito.org/Downloads/corn-20150827.tar.gz - description found - on http://www.inpito.org/projects.php the Corn Library project. It's very simple but I believe it is affective.
... End on e-mails ....
Who knows, once I get a class taught, using Slackware, I may be able to rely on their aid.
Thank you for the information ... I did do a quick look at link.
I've have to give it a more in depth look some time in the future, as I am currently working on a "write access" problem over an NFS mapped drive connection.
I guess, I total missed Amarok in the TDE git repository fetch that I did ... sure I can tale a look at it to see if I can get it to compile.
Here is my own personal build list. When I get a Slackware machine setup with a custom kernel and/or Graphic Drivers, I have a build script that steps through and builds and installs all the following package automatically without any interaction from myself. Some programs are compiled and installed simple as dependencies to other programs that I could not get to compile, but I just decided to leave them in anyway, just in case I figure out the problem with the program I was hoping to reach. Anyway ...
Many thanks for providing Trinity for Slackware. I didn't have any experience with trinity before. Amazingly it is more lightweight and bug free than Xfce on my laptop. just one issue: Restart and Turn Off buttons only terminates X and don't reboot/shutdown my system.
I have the same problem too, unfortunately; I have not had the time to discover the problem, and fix it, so I simply give a quick press of my power button on the computer, after terminating X, as a quick press of the power button, has always seemed to produce a soft shutdown on my computers, after terminating X. Also, the tdevdesigner crashing when I try to use it, because of a missing shared library called "linux-vdso.so.1" so at some point in time, hopefully, I'll get things like these fixed. What I really need is a working "Time Pause Machine" or find the watch from the movie "Clockstoppers".
If I find a quick fix for the power down and/or reboot thing, in the near future I'll post it.
Thank You everyone for your posts!
If you have any more questions about my Trinity build, don't be afraid to ask.
Last edited by Stragonian; 01-21-2016 at 04:21 PM.
Another minor issue: keyboard layout is not switchable by keyboard shortcuts. I tried many keyboard maps and many keyboard shortcuts via xkb configuration but nothing achieved.
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 install additional packages to your /usr/local directory you'll need to decide whether to proceed with this option.
Quote:
Originally Posted by ruario
Out of interest, why do you do that and what has it got to do with Trinity install? Or to put it another way, why would this be part of the instructions?
I still want to know what this is all about. Firstly, I personally think this seems like a silly idea. If you don't want to use /usr/local, don't use it but why symlink it back to /usr and increase the likelihood of breaking your main install when a self-compiled and installed package now overwrites a system provided file in /usr? Secondly, in what way does this relate to Trinity installation? It feels like you have just inserted an arbitrary (poor) personal preference for no good reason. Sure you have a warning now but that does not entirely excuse it IMHO, since less experienced users who just want to try another desktop environment are more likely to follow the steps verbatim to avoid something going wrong. They will then be left with this misconfiguration.
If you feel this is truly needed for some reason, perhaps you could explain why and someone here may be able to suggest an alternative rather than encouraging a non-standard and potentially harmful step.
P.S. That step feels like it belongs on another page, called something like "Changes I like to make to my system", with a list of such tweaks and an explanation of why each is done so that the reader can evaluate if it makes sense for him or her.
Last edited by ruario; 01-22-2016 at 04:56 AM.
Reason: added the postscript
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.