Thanks.

I found today that using only qt3 is not going to cut it when wanting to build other packages such as tdebindings. I got the base Trinity packages compiled, but building tdebindings failed. Time to go back and build tqt3 and try with that. At the moment when compiling tqt3 to /usr it fails during make trying to find libtqt-mt.so.3

I am one of the maintainers of Porteus, a lightweight slack based distro born from the inactivity of slax. My current Trinity base package weighs in at 55Mb (compressed). kdep-apps and koffice are separated to afford users the choice. Stripped back to just the Trinity package and base requirements the final iso would be around 170Mb.

Jay

On Thu, Jan 26, 2012 at 6:11 PM, Darrell Anderson <humanreadable@yahoo.com> wrote:
> I decided to go for installing everything to /usr as this
> will be for a custom stripped slackware distro with only
> lxde and Trinity.  I also went with qt3. Everything
> compiled nicely for me. Arts seems to be happy in this setup
> now ... at least i will take the final output from building
> arts to be an indication of success:

Yes, just for those who watch the list, installing to /usr is fine as long as KDE4 is not installed to /usr.

There are a few Slackers here. Welcome!

For myself, although I don't use KDE4, I limit my Slackware builds to /opt/trinity because my packages are used by other people. As the stock Slackware comes with KDE4, I have to accommodate that. I also test and watch for potential conflicts with KDE4. When R14 is released, I likely will build a special set of packages for myself to install to /usr.

As you are a Slackware user, I welcome any help you can offer the Trinity project. We need more exhaustive testing. Install to /usr for yourself, but if you have the time and spare CPU cycles, please help to build GIT in various scenarios to find any breakage. Finding that breakage now will mean no breakage when R14 is released.

In addition to testing various build scenarios, we need better testing to ensure no conflicts with KDE4.

tqt3 will be the future and eventually will replace qt3. I build with both right now for testing purposes.

As you mention Trinity and LXDE in the same sentence, I presume you are interested in light weight desktop environments. I am interested in any information you might have that will help create a "Trinity Light" for older hardware. The idea of Trinity Light is not so much a separate or unique build of Trinity, although that could happen, but includes any ideas to customize Trinity for older hardware. Once upon a time I addressed the topic with KDE 3 (http://humanreadable.nfshost.com/howtos/optimizing_kde.htm), but I'd like to see a wiki article with various tips and ideas to get Trinity to run on old hardware, which should include build options. People running old hardware are unlikely to need every option built into Trinity and any related information we accumulate about these topics will help.

Darrell


---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net
For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net
Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting