Trinity Desktop for Slackware-13.37 i486 and x86_64
I've gotten the base Trinity Desktop for Slackware-13.37, i486 and x86_64 Multilb System, as the native desktop. I am sure however, I will encounter more problems as I continue to compile more of the packages that are apart of the build. So I am creating this thread as a place to discuss the problems as they arrive.
For more information, see: http://www.inpito.org/trinity.php The page describes what I've been doing with the Trinity 3.5.13 desktop. |
Great! KDE3 is a much more efficient desktop for working than KDE4. Thanks for sharing!
|
Unfortunately, my website isn't up as often as I like. So if it's down give it some time, the page is there. I think it's a DNS record problem with my hosting provider as I can ping the IP address, it just can't resolve the host name. The last recorded HTTP request that was successful was at [19/Jun/2012:16:57:04 -0500], so as of right now its been down for about 4 hours. I hope it comes back online soon.
|
It seems that kdebindings 3.5.13 can't find kdelibs.
Code:
checking for KDE... libraries /usr/lib64, headers /usr/include Code:
./configure --prefix=/usr --sysconfdir=/etc/trinity --libdir=/usr/lib64 --mandir=/usr/man --enable-libsuffix=auto --with-qt-dir=/usr/lib64/qt3 --with-qt-includes=/usr/lib64/qt3/include --with-qt-libraries=/usr/lib64/qt3/lib64 --with-extra-includes=/usr/lib64/tqt3/include --with-extra-libs=/usr/lib64/tqt3/lib64 --enable-dependency-tracking --enable-closure |
Added gtk-qt-engine-3.5.13
I added gtk-qt-engine-3.5.13 to the list. http://www.inpito.org/trinity.php For those who like a consistent looking desktop.
|
But that build packages requires HAL
|
I have been testing and using Trinity on Slackware 14. :)
To build without HAL requires building from GIT using the new TDEHW libs support, which also requires pmount. In my build scripts that explicitly look for HAL, such as tdebase, I do this: Code:
if [ -x /usr/sbin/hald ]; then The existing 3.5.13 and upcoming 3.5.13.1 release does not contain TDEHW libs support. I tinkered a bit with creating my own HAL package, but had mixed success. TDEHE works nicely. |
By the way, I'm sending this specific comment from Firefox 15.0.1 in Slackware 14 64-bit running Trinity from the latest GIT, built last night while I slept.
So yes, Trinity does build and install in 14. :) Being the development branch, bugs exist, some work-arounds and build patches are needed, but I find Trinity stable and usable. :) |
Could you make the packages available for testing?
|
Quote:
Trinity Desktop for Slackware |
Quote:
|
The significant changes are to the Trinity sources, to comply with GCC 4.7.x, glibc, libpng, etc; and to package names. All of that has been fixed in GIT and most if not all of those same build issues were back ported to the upcoming 3.5.13.1. My build run for the main packages and several others takes about 6 hours. To get TQt3 and the core packages built requires about an hour and a half. Building the core provides a basic testable environment. The "time consuming" part is renaming package names in the build scripts.
|
Quote:
Cheers! |
Quote:
|
Try this:
http://humanreadable.nfshost.com/mis...ildtree.tar.gz I will not guarantee how long I'll keep the file available. :) Unpack the archive to an appropriate build directory. I have not been publicly supporting this for a while --- don't be surprised the docs are outdated. That said, I have been using Trinity pre-R14.0 from GIT for a long time and am building a new package set right now. Just run ./TDE.SlackBuild. I have things configured as a two-step build run. The first step is to build TQt3. The second step builds all remaining packages. Use the SUITE=false option to build beyond the basic package set and use SUITE=false ALLAPPS=true to build more packages. Like so: SUITE=false ./TDE.SlackBuild or SUITE=false ALLAPPS=true ./TDE.SlackBuild These build scripts presume a local GIT repository. Currently there is no upstream project support for GIT source tarballs. Source tarballs are available only for official releases. Once upon a time my build scripts supported making tarballs, but I haven't tested in a very long time. The build scripts in the archive are horribly complicated because I'm part of the testing team and I need to support more than a typical user. Feel free to whittle the build scripts to the bare essentials, although you'll still need a local GIT repository or to make your own source tarballs. I don't have time but would be nice if somebody hacked the build scripts to something that could be maintained at slackbuilds.org. Take a look at the Slackware KDE 3.5.10 build scripts for 12.2 for an example how to streamline the build scripts to the essentials. By coincidence, the pre-R14.0 sources are going into hard freeze tonight. That means focus is changing from testing anything to only fixing certain bug reports for the next weeks. An official R14.0 should be released within the next several weeks. At that time official source tarballs will be available, which will render things easier for many folks. Last note: There are foundational changes in the upcoming release (the desktop still looks the same :)). Don't mix and match GIT with 3.5.13.X. Stick with one or the other until R14.0 is officially released. :) |
Thanks, Woodsman! I'm gonna give it a try once I learn what you mean by 'local GIT repository'. Does that mean I need to download all the TDE tarballs into a directory on the hdd I'm going to build TDE on?
Meh...I don't think I have the brain-power to do this, lol. What was that movie from years back where someone said "I'm so confused!"? I'll take a plug at it on my secondary hdd and if I screw anything up, no biggie as I can just install Slackware again like nothing happened. |
A local GIT repository is a local mirror of the upstream source tree. Similar to the way the Slackware Current sources are available but with no tarballs. You can view the Trinity sources here:
http://git.trinitydesktop.org/cgit/ Although allowing faster compilation, a local copy of the source tree is not needed. Yet I never tested the build scripts with trying to pull the sources on-the-fly from the upstream GIT repository. Feel free to tinker and improve. Possibly update the scripts to pull the sources from upstream and make a tarball on-the-fly. Do anything you think will make things easier for you and others. My time is limited but I'll help as I can. As I mentioned, I'd like to see somebody massage the build scripts for more general usage. BTW, like Slackware Current, technically the Trinity GIT branch is the testing branch. Yet I find everything remarkably stable. |
Quote:
|
Isn't it the link in the post right above yours? http://git.trinitydesktop.org/cgit/
|
Quote:
However, when I run git clone http://git.trinitydesktop.org/cgit/tde TrinityDesktopEnvironment I get a bunch of empty sub-folders. Is my git command or url wrong? |
Try this:
http://www.trinitydesktop.org/wiki/b...Developers/GIT Then try this: http://www.trinitydesktop.org/wiki/b...ers/HowToBuild If that fails, consider joining the Trinity developer's mail list. :) |
Woodsman,
Good Afternoon! Would you mind explaining me about Trinity hibernate or suspend modes. Is it possible to use it after an idle time? And is it using a hal pacakge yet? |
Trinity 3.5.13.2 uses HAL. Trinity git, that is, the next official release hopefully in the upcoming weeks, has its own internal detection mechanism and HAL is not required but still supported. Trinity supports upower. I've been using Trinity git for a few years. Since February 2013 I've been using Slackware 14.0 and I always build Trinity packages without HAL support.
I'm not recalling serious or major bug reports about Trinity and upower, etc. |
Quote:
|
I am anxious for it. Why not a Slackbuild idea?
|
All times are GMT -5. The time now is 11:33 AM. |