Re: [trinity-devel] qiomanager_p.moc vars not declared

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