Trinity Desktop for Slackware(64) 14.1 + Multilib System
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.
I do the symlink to /usr/local to fix a large number of programs that have problems auto-configuring to find some library files in linux - currently I compile the following packages on Slackware 14.1 -
<snip long list of apps apparently some having problems with /usr/local>
Some of these programs I could get rid of, or replace with others, but once again ... time is needed. the symlink - is a quick way to fix the lack of auto-configuration in some of these programs. ... although most of them do OK.
Now I have TDE running on my secondary, a 14.2 32 bit system, and it's pretty sweet but I was surprised that TDE's footprint is only slightly lower than the default Plasma on 14.2. I like to use /usr/local for some apps and it would be nice to be able to run both Plasma and Trinity on the same system and I'm wondering why simply installing in /opt/ wouldn't solve both those concerns. Since that location was default for a generic install of TDE, I'm also wondering why changing that was desirable?
After spending some time on TDE Trinity and being pleased with it's speed and intuitive nature but aware that it lacks a few of the modern accommodations I am very curious as to why,. with all the hoopla over low resource WM/DEs that neither TDE Trinity nor any of the LXDE varieties has even ever made it to a single full release? Odd.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.