The "My Documents" device icon dialog box was broken but partially repaired in SVN 1176545.
The dialog box no longer appears, but when the $HOME/Documents directory does not exist then Konqueror opens with an error message.
The Konqueror error message indirectly reveals the solution to competant computer users, but might not be obvious to the less technically inclined.
Similar behavior is found when selecting "Documents Folder" from the K-Menu, which results in an error message that the $HOME/Documents does not exist.
A more elegant solution for both would be to provide a Yes/No/Cancel dialog box stating the directory does not exist and asking permission to create the directory.
I think $HOME/Documents is specified somewhere as a default, but any associated dialog box should provide a text box allowing more technically inclined users to change the location of that path.
Darrell
I have created a set of pre-release source tarballs for Trinity 3.5.12.
They are currently publishing to the mirror, and should be available
within 48 hours from this link:
http://ppa2.quickbuild.pearsoncomputing.net/redirect.php?file=releases/3.5.…
If no issues are found in the next four days, there is a very good chance
these files will become the final release.
Please keep this information on this list for now; I am releasing the
files early for testing purposes only, not for general consumption.
Thanks!
Tim
Hi,
Being that 3.5.12 is on the verge of being released, I've decided to
include this release in BLFS to replace the aging 3.5.10.
Given that KDE 4 has rapidly changed quickly, we can't keep up with
the pace, and that stupid cmake.
I've also decided to build RPMs of the KDE 3.5.12 release. They'll be
built for Mandriva, Fedora, and SuSE :)
What configure options would you recommend for stuff like this?
I saw a thread on trinity-devel, but given the fact that I just
subscribed (when I should have done so earlier -.-"), I don't have the
emails.
--
later, Robert Xu
Hello,
As I see, in kde4 api-dox are not handled anymore by building system (actually
apidox is not handled by autotools anyway in kde3, but by script named
doxygen.sh). Is there any reason to include apidox support in cmake scripts?
--
Serghei
I'm wrapping my head around something new.
In the past I have been copying the svn package contents to tmpfs and working there with my compiles. That habit came from being accustomed to building packages from a source tarball. The source tarball is unpacked to a temporary working area and then compiled. With svn, something to which I am new, I maintained that habit by copying the package contents.
Trinity is huge and compiling the entire core package suite requires 6 hours even on a dual core system. I could live with that if I knew the packages always compiled 100% of the time. That is a normal expectation with tarballs, but is not the case in a dynamic svn environment. There always is some degree of breakage. Hence a previous suggestion to use ccache.
I have compiled kernels for many years. Being new to svn I did not understand that, much like the kernel, I don't have to image package sources from the svn tree but can work directly in that directory. Like the kernel I need only use 'make clean' to restore the svn tree. I then can use ccache to create compiling caches, which should dramatically reduce compile times.
If I understand correctly, then in my build scripts I need to do the following:
================================
WAS:
(snippet from arts package build script)
echo "Copying $PRGNAM source files to $TMP..."
cp -a $SVN_SOURCES/dependencies/$PRGNAM $TMP/ || exit 1
cd $PRGNAM || exit 1
echo
echo "Building make and config files..."
echo
echo "Package will be stored at $OUTPUT."
echo
cp -p "$LIBTOOLM4" admin/libtool.m4.in
cp -p "$LTMAINSH" admin/ltmain.sh
make -f admin/Makefile.common
echo
echo "Finished building make and config files."
echo
chown -R root:root .
CFLAGS=$CPUOPT \
CXXFLAGS=$CPUOPT \
./configure \
--prefix=${PREFIX} \
--sysconfdir=${SYSCONFDIR} \
--libdir=${LIBDIR} \
--disable-debug \
--program-prefix="" \
--program-suffix="" \
--build=$ARCH-slackware-linux
make $NUMJOBS || exit 1
make install DESTDIR=$PKG
================================
CHANGE TO:
echo "Changing to $PRGNAM source files in SVN..."
cd $SVN_SOURCES/dependencies/$PRGNAM || exit 1
echo
echo "Building make and config files..."
echo
echo "Package will be stored at $OUTPUT."
echo
cp -p "$LIBTOOLM4" ./admin/libtool.m4.in
cp -p "$LTMAINSH" ./admin/ltmain.sh
make -f ./admin/Makefile.common
echo
echo "Finished building make and config files."
echo
chown -R root:root .
make clean
if [ -x /usr/bin/ccache ]; then
CC="ccache gcc"
echo "Using ccache. Unless configured otherwise, the cache is stored in $HOME/.ccache."
echo
else
CC="gcc"
fi
CFLAGS=$CPUOPT \
CXXFLAGS=$CPUOPT \
$CC ./configure \
--prefix=${PREFIX} \
--sysconfdir=${SYSCONFDIR} \
--libdir=${LIBDIR} \
--disable-debug \
--program-prefix="" \
--program-suffix="" \
--build=$ARCH-slackware-linux
make $NUMJOBS || exit 1
make install DESTDIR=$PKG
================================
Do I have the correct idea?
Thanks much!
Darrell
I have been thinking how we might provide binary packages for Slackware 12.2
I'm hoping that if binary packages are available, in addition to build scripts at my site, that interest will increase among Slackware users. Although many Slackers build their own packages, many do not. Yet if they can download the final packages they might spark new interest in Trinity.
I don't have the bandwidth at my meager web site to host packages.
You have offered to host packages. How do we want to do this?
If we wait until the official 3.5.12 tarballs are available, I can build those final packages. I just need to get them to you.
We would need to post and test a link at your web site just like the other links.
If we coordinated this then you could include Slackware 12.2 as part of your release announcement.
Darrell
Nice screen grabs. I'll mildly recommend choosing non-Kubuntu branded screen shots. Otherwise people will think Trinity is Kubuntu-specific. That seems to be the consensus opinion when browsing the web. The fact that Trinity now builds and runs on Slackware 12.2 might somewhat alleviate that belief.
I revised the text and editorialized. No screen shots yet (I don't yet know how), but please review.
I don't have the hang of how to use the online editor. I don't know why when I paste text from a text editor the entire text is enclosed in a gray box. Please share if you know why or how to fix. I don't find the editor at all intuitive or friendly.
When were the KInfoCenter options moved to KControl?
Darrell
Looks like everything builds that I try to build. That is good news! Yet there remain some build issues.
I can't build libcarddav. For me that is a luxury package. I won't cry if the package is not installed. Yet I presume a handful of people will want to use the package. libcaldav builds fine here.
Do I presume correctly that libcaldav provides some additional functionality although libcarddav is not installed?
I can't build tqtinterface directly within the SVN directory. I have to copy the tqtinterface tree to a temporary location and build clean from there, much like building from a tarball. I can build tqtinterface within the SVN directory only once. Thereafter the build always fails. I can build all other packages directly within the SVN directories.
Is this a bug with tqtinterface?
I seem unable to build any package after I run 'make clean' within each package SVN directory. Perhaps this is a conceptual error on my part in the way I use the command in my build scripts. Yet seems that occasionally I should clean house before attempting a full build run.
What is the correct way to clean house in SVN?
I configured my build scripts to ccache. Yet I see no difference in build times. There are files in the cache, the log updates, the log and stats show there are cache hits. Yet the process took 8 hours overnight to build all core, support, and several non-core packages. I don't know whether 8 hours is the best I can do or whether I have something configured incorrectly.
Anybody have theories why I see so little difference?
I need to test building from source tarballs rather than svn.
Although not yet official, can we get a web link for developer testing of 3.5.12 source tarballs?
I still have about a half dozen non-core applications that need build scripts and testing. I use those packages regularly and at least those non-core packages need my attention if I am to fully embrace Trinity.
I have yet to test building the core packages with external support packages installed such as krb5, avahi, lua, OpenEXR, GraphicsMagick, and PostgreSQL.
Although I now presume a hard freeze except for fatal bugs, several non-fatal bugs and usability issues slipped through untouched in our recent discussions. I will sift through the discussions and submit formal bug reports and feature requests in the bugzilla.
Darrell
