I have now successfully packaged the following for Arch Linux with the
PKGBUILDs and some bash scripts for building this set.
They will need to be built using a clean chroot see this link for
explaination:
https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_Clean_Chro…
The PKGBUILD script will show the dependencies for each package.
I will moving on to the applications shortly, I need a little break ;)
If anyone is interested i have placed the scripts here:
git clone https://github.com/baho-utot/trinity.git
until they can be incorperated into the tde-packaging repo.
#
# Dependencies
#
qt3 - autotools - complete
tqtinterface - cmake - complete
arts - cmake - complete
dbus-tqt - cmake - complete
dbus-1-tqt - cmake - complete
#
# Desktop
#
kdelibs - cmake - complete
kdebase - cmake - complete
kdebindings - not needed - not needed
kdeaccessibility- autotools - complete
kdeutils - autotools - complete
kdemultimedia - autotools - complete
kdeadmin - autotools - complete
kdeartwork - autotools - complete
kdegames - autotools - complete
kdetoys - autotools - complete
kdeedu - autotools - complete
kdepim - cmake - complete
kdesdk - autotools - complete
kdeaddons - autotools - complete
kdevelop - cmake - complete
kdewebdev - cmake - complete
kdegraphics - cmake - complete
Thanks to everyone
I wanted to share a few things about kdemultimedia.
First I didn't see akode in the repository, but I have a copy of
akode-2.0.2. With a small patch to allow it to build with gcc-4.6.1, I
was able to install it with:
sed -i "s/#include <iostream>/&\n#include <cstdlib>/" \
akode/lib/auto_sink.cpp
sed -i 's@#include "../lib/decoder.h"@&\n#include <cstdlib>@' \
akode/akodeplay/akodeplay.cpp
sed -i "s/<assert.h>/&\n#include <string.h>\n/" \
akode/lib/player.cpp
sed -i "s/<iostream>/&\n#include <string.h>\n/" \
akode/lib/magic.cpp
./configure --prefix=$TRINITY_PREFIX --without-ffmpeg
make
If you want the patch (2 lines change), I'd be glad to send it. I
should probably put that and the seds above into one patch.
-----
Second, I was able to build kdemultimedia, but one module had a problem
picking up where tqt was located. The following did work for me:
cp -v /usr/share/aclocal/libtool.m4 admin/libtool.m4.in
cp -v /usr/share/libtool/config/ltmain.sh admin/ltmain.sh
sed -i -e "s@/usr/include/tqt@$TRINITY_PREFIX/include/tqt@" \
admin/acinclude.m4.in
make -f admin/Makefile.common
sed -i -e "s@^gentable_LDADD.*$@& -L$TRINITY_PREFIX/lib@" \
noatun/library/Makefile.in
./configure --prefix=$TRINITY_PREFIX \
--with-qt-dir=$QTDIR \
--enable-closure \
--with-vorbis \
--with-alsa \
--with-audiofile \
--with-flac \
--with-akode \
--with-extra-includes=$TRINITY_PREFIX/include \
--with-extra-libs=$TRINITY_PREFIX/lib:$QTDIR/lib &&
#--with-xine \
#--with-cdparanoia \
#--with-lame \
#--with-theora \
#--with-gstreamer \
#--with-kscd-cdda \
make
I still need to add some more prerequisites and test some more, but the
PKGBUILD for kdemultimedia indicated akode wasn't available, so I
thought I'd share.
-- Bruce
I created an etherpad containing TDE application descriptions. I extracted much of the information from Helpbook abstracts and then massaged the information accordingly. The extraction process was not fluid or easy to read, even after cleanup. I suspect a few apps are missing from the list.
The descriptions are more or less grouped the same as the T-Menu.
Everybody please feel free to edit the list as needed.
Tim, Calvin:
In my web site improvement suggestions I recommended an applications description page. Ideally, we should have full web pages for certain apps, but this list will provide a nice start.
Darrell
Is anybody else experiencing this? For example if I manage files outside of Konqueror, the file pane does not automatically update. I have to refresh the pane to see the changes.
Is there a config setting that could affect this?
Darrell
With SVN I used a package naming scheme based upon the previous official release number and SVN version:
kdebase-3.5.12-125202-i486-1.txz
With the official tarballs the package name excluded the SVN version:
kdebase-3.5.13-i486-1.txz
I expect to continue that naming scheme with official release tarballs, although the version numbers change:
kdebase-r14.0-i486-1.txz
Enter GIT.
GIT uses a weird hash number for each patch version. Is there a more straightforward version number? Or will I have to start naming GIT builds using a date and time scheme?
kdebase-20120101_2200-i486-1.txz
More generally, should we adopt a common package naming scheme, as much as possible within the limitations of each distro's package naming conventions? Might be nice if all of us use a somewhat similar naming scheme.
Ideas? Comments?
Darrell
I've been trying to sort out kdenetwork-3.5.13 dependencies for those
users who may only want to create a partial build of kdenetwork.
I've applied the patch in git, but it looks like one file has not been
fixed. phonesessionclient.cc still points to tqname.h.
I've added the following to my build script:
CLIENT="kopete/protocols/jabber/jingle/libjingle/talk/session/phone/phonesessionclient.cc"
sed -i -e 's/tqname.h/qname.h/' $CLIENT
Whew! Eight directory levels!
However, the sed allows the program to complete the build. I've still
got a bit of research to do, but I will create a new patch for LFS and
send it to you unless you do it first.
-- Bruce
Greetings All,
Almost a year ago, January 31st exactly, I first emailed Timothy Pearson
about helping out with Trinity. I wanted to create an improved website and
start contributing. Soon I found that I was I could. This has manifested
itself in fixing up some bugs, getting trinity on arch, working on the
website, planning meetings - everything here and there and in between. Oh
my how a year passes.
I proudly announce whenever the topic arises that I help contribute and
develop the traditional desktop. I am so very proud of everyone involved.
For a small development team and limited resources, I think everyone is
doing an amazing job. We have a dedicated user base that is growing
everyday. Trinity is well on it's way to becoming a Linux household name.
Looking back at this year we had some bumps in the road. The release of
3.5.13 was originally scheduled for the first half of the year. Then in
June we had a 2 week outage of Tim's servers. We Had a bit of a bumpy (yet
successful!) release of 3.5.13 with some mirror problems and we've had to
fend off various folks as well as keep the masses calm. But we also release
a great product. Trinity Desktop 3.5.13. What a release! It has paved the
way for great things to come. We closed a whole host of bugs, and finally
have packages available for all of the major distributions, thanks to our
dedicated packages. Beta ARM support and other awesome technical feats by
timothy have never failed to impress me.
The 3.5.13 release has set us up to put out an even better R14 release, and
looking into the next year I foresee greatness! Trinity rising triumphantly
out of the ashes of the Linux desktop world, soldering in tablet interfaces
and lack of configuration. Like a phoenix out of the ashes! ;)
But seriously, thank you so much to everyone who has contributed! Thank you
to Baho and L0ner, my newly found archlinux packages. To Darrell the
unrelenting bug reporter, who has helped us work though many an issue. To
Laurent who has provided technical help many a time on the lists. To Robert
Xu, my good friend and ally, who has helped lament a season of Chemistry
and Physics induced headaches. To David Hare, Kate Draven and Dr Nikolaus
Klepp who have helped end users needs by answering repeatedly on the
trinity-users mailing list. Thank you to everyone I haven't mentioned,
there are simply to many.
Most of all I want to pitch my undying support for our tireless leader,
Timothy Pearson. His work on Trinity has enabled all of us to come together
and move forward. He has guided us through 3 successful releases and will
lead us to many more. Tim is an excellent computer programmer and also a
amazingly calm and reserved gentleman. Hats of to Tim and a round of
applause!
I am so excited for R14, and I'm really excited in the direction we are
heading, let's make Trinity the best it can be.
A Merry Christmas and a Happy New Year,
Calvin Morrison
I've been struggling a bit with building kdeadmin-3.5.13.
First the instructions on the HowToBuild page are a bit confusing:
1. Regenerate Autoconf/Automake files
cp -Rp <path to your system's libtool.m4 file> admin/libtool.m4.in
cp -Rp <path to your system's ltmain.sh file> admin/ltmain.sh
make -f admin/Makefile.common
Why the -R in the cp command? -R, -r, --recursive all mean the same
thing, but are not really meaningful if the source is a file and not a
directory. I'm not sure the permissions are meaningful either. I'd
just use --verbose.
2. Configure and Build
./configure --prefix=${PREFIX} --sysconfdir=${SYSCONFDIR} \
--libdir=${LIBDIR}
make
This is where I get into problems. I have qt in /opt/qt and Trinity
base in /opt/trinity. Configure fails to find tqt and then thinks it's
version 4. It doesn't find qt and fails. This can be overcome with:
CPPFLAGS='-I/opt/trinity/include/tqt' \
./configure --prefix=/opt/trinity ...
The --with-qt-includes option does not solve the problem, but the
CPPFLAGS can be either before or after ./configure.
Environment variables are:
PATH=/opt/trinity/bin:/usr/local/bin:/bin:/usr/bin:\
/opt/texlive/2011/bin/x86_64-linux:\
/opt/llvm/bin:/opt/qt/bin:/opt/xorg/bin:/sbin:/usr/sbin
PKG_CONFIG_PATH=:/opt/trinity/lib/pkgconfig:\
/usr/local/lib/pkgconfig:\
/opt/qt/lib/pkgconfig:\
/opt/xorg/lib/pkgconfig:\
/opt/xorg/share/pkgconfig
QTDIR=/opt/qt
Then the make fails in several places. What I finally found that works is:
make LDFLAGS='-lqt -lkdecore' \
TQTDCOPIDL=dcopidl2cpp \
TQTDCOPIDL2CPP=dcopidl2cpp
This again tells me that configure didn't do it's job. In the Makefile,
both TQTDCOPIDL and TQTDCOPIDL2CPP are blank. The LIB_KDECORE variable
is set correctly but is not used. LIBTQT_LDFLAGS is set to -ltqt, but
that doesn't do the job.
There are two programs in /opt/trinity/bin: dcopidl2cpp-tqt and
dcopidl-tqt, but they do not work with the input in the Makefile.
I did not have any of these problems in KDE3. Is there something I'm
missing here?
-- Bruce
FYI
Here is an updated status on my progress on building TDE for the Arch liubx
distro. I am going to place all the pkgbuild files into a git repository.
I will be starting on some of the apps shortly.
Is there a place on the trinity website where the 3.5.13 indivual source
tarballs are stored?
I need this so I can place the url into the build scripts so that the package
management system that builds source on arch linux can download by package as
needed.
qt3 - complete 2011-12-22
tqtinterface - complete 2011-12-22
arts - complete 2011-12-22
dbus-tqt - complete 2011-12-22
dbus-1-tqt - complete 2011-12-22
kdelibs - complete 2011-12-22
kdebase - complete 2011-12-22
kdebindings - not needed
kdeaccessibility- complete 2011-12-23
kdeutils - complete 2011-12-23
kdemultimedia - complete 2011-12-23
kdenetwork - barfed
kdeadmin - complete 2011-12-23
kdeartwork - complete 2011-12-23
kdegames - complete 2011-12-23
kdetoys - complete 2011-12-23
kdeedu - complete 2011-12-23
kdegraphics - barfed
kdevelop - complete 2011-12-23
kdeaddons - complete 2011-12-23
kdewebdev -
kdepim - complete 2011-12-23
kdesdk - complete 2011-12-23
Thanks
