trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: October 2011

Re: [trinity-devel] Trinity 3.5.13 Release Date

From: /dev/ammo42 <mickeytintincolle@...>
Date: Sun, 23 Oct 2011 02:42:50 +0200
Le Sat, 22 Oct 2011 09:02:29 -0700 (PDT),
Darrell Anderson <humanreadable@...> a écrit :

> > > > > 1. Are there any apps that have not been
> > converted to
> > > > cmake?
> > > > 
> > > > The majority have NOT been converted, but the
> > automake
> > > > build system has
> > > > been repaired for the remaining apps and
> > therefore works
> > > > perfectly with
> > > > the latest versions of Autotools.  The main
> > ones that
> > > > are production ready
> > > > are:
> > > > 
> > > > tqtinterface
> > > > arts
> > > > kdelibs
> > > > kdebase
> > > 
> > > > Others have been converted but I am not using the
> > CMake
> > > > versions of them
> > > > in the Debian/Ubuntu builds, so I cannot vouch
> > for
> > > > completeness/correctness of the build files.
> > > > >
> > > 
> > > Therefore use cmake for those four packages and
> > automake for all
> > > others?
> > > 
> > > > > 3. Is 3.5.13 going to include bug fixes or
> > is the
> > > > conversion to cmake the
> > > > > limit for that release?
> > > > >
> > > > YES!  Lots of bug fixes are in SVN; see
> > > > http://trinitydesktop.org/patches/ for a
> > taste of what is to come.
> > > 
> > > I ask because I submitted many bug reports and most of
> > them remain
> > > open. A handful are critical if I am to migrate from
> > KDE 3.5.10 to
> > > Trinity. If I had to whittle my list to a few hopefuls
> > for 3.5.13:
> > > 
> > > 293   Kde-config Incorrectly Creates a Profile Folder in the
> > > System root directory 388   KDESU Dialog Box Behavior
> > > 393   Incorrect kdesu Behavior When Opening Kate
> > > 394   Problems with DCOP After Using kdesu
> > > 296   New Trinity Profile Error Messages
> > > 335   Konqueror Icon Activation Effect
> > > 389   Activation Effects
> > > 385   Unmounted removable device icons do not appear on the
> > > desktop 303   Safely Unmount does not always remove the icon from
> > > the desktop 258   ksmserver: Logout confirmation fadeaway is too
> > > slow with older hardware
> > > 
> > > Some or all of these bugs might have been resolved
> > without the
> > > developer being aware of a bug report. Building and
> > testing the
> > > packages will go far to help and might be the only way
> > to confirm the
> > > bug is resolved. I hope to attempt building soon,
> > which is why I
> > > started this thread, but did not want to start if
> > development was
> > > still in arrears.
> > I have successfully built the dependencies, kdebase and
> > kdelibs
> > checked out from SVN on September 9th on my Slackware64
> > 13.37 system:
> > -Everything is installed into /opt/kde3 prefix
> > -the Qt3 SlackBuild I used is attached; it builds Qt3
> > cleanly and
> > successfully (I didn't see the problems mentioned by
> > Patrick
> > Volderking in his build script, and kdebase/kdelibs builds
> > and runs).
> > -the poppler-qt3, qca1, qca1-tls SlackBuilds from the
> > kde-3.5.10-for-slack13.0 build well once that the
> > hard-coded path in
> > the qca1-tls build script is updated
> > -the basic global configuration is in the kdeetc3 tarball.
> > This
> > configuration doesn't stop KDE4 from running, and if KDE4
> > is installed
> > one just has to
> > $ unset KDEDIRS
> > before running Trinity.
> > -for packages from the SVN tree I used a single CMake build
> > script (the
> > "build" file of the tarball).
> > > 
> > > Darrell
> 
> Thanks much. :)
> 
> If you are running Trinity SVN on Slackware, which is what I use too
> (13.1), if you have the time would you run some simple tests on the
> bugs I listed? I hope to soon start testing the build process again
> and hopefully thereafter I can more thoroughly test the bugs.
> 
> Darrell
293: if I have a root account and run
# kde-config --help
it creates a .trinity directory.
393: kdesu /opt/kde3/bin/kate doesn't use root settings, tries to
use /tmp/kde-guest directories (instead of /tmp/kde-root) but can write
to / (so has root privileges).
394: I can reproduce the bug and can add that after kdesu'ing kate,
the /tmp/kde-guest/ksycoca belongs to root (!)
I could not test immediately other bugs (for exemple, for 258, my
compiled Trinity is x86_64…), but if I find the time I can probably
correct some of those.