Here is a quick forward from the Arch list regarding Trinity binaries for Arch
Linux (svn)
-----------
All,
Kaiting Chen has provided server space for Trinity binaries. Currently I have
the i686 files uploaded and will upload x86_64 shortly (after my kids are done
with toontown....)
The url for the i686 repo is:
http://www.kiwilight.com/~drankinatty/trinity/i686/
(Trinity packages are 2/19/2011 builds)
The x86_64 repo will be the same url with x86_64.
Trinity needs a clean environment currently (no kdemod3). If you have had a
prior kdemod3 install, then delete:
/var/tmp/kdecache-$USER/ksycoca
/var/tmp/kdecache-$USER/ksycocastamp
and move ~/.kde somewhere else.
If you have kde4 installed, then expect akonadi/nepomuk and all the kde4
autostart files in /usr/share/autostart to run (Trinity devs are working on a
way to ignore all the kde4 autostart files)
To install trinity, just add the repo to /etc/pacman.conf:
[trinity]
Server = http://www.kiwilight.com/~drankinatty/trinity/i686/
Then just do 'pacman -Sy trinity-kdewebdev' and it will pull in the complete
Trinity desktop (kdewebdev requires all trinity dependencies)
I recommend installing it in either a clean Arch install, or just create a new
Arch virtualbox VM and install it there. It is a darn good looking desktop.
x86_64 packages by the morning :)
See: https://wiki.archlinux.org/index.php/Trinity for current details :)
--
David C. Rankin, J.D.,P.E.
--
David C. Rankin, J.D.,P.E.
All,
Here are recent build times for Trinity svn on a middle of the road P4 3.2G
box. (nothing special - old Dell GX280 'small form factor'):
10:55 supersff:~/tblds> grep Feb bldlog.txt
Feb 19 01:44:45 building: trinity-qt3
Feb 19 02:06:12 building: trinity-pyqt3
Feb 19 02:17:05 building: trinity-tqtinterface
Feb 19 02:18:16 building: trinity-arts
Feb 19 02:22:02 building: trinity-kdelibs
Feb 19 03:01:01 building: trinity-kdebase
Feb 19 03:36:42 building: trinity-kdevelop
Feb 19 03:51:13 building: trinity-kdewebdev
Feb 19 03:58:21 done!
2:14 beginning to end. For anyone packaging Trinity, the basic 'outline' of
the build script layout I used was (link to full script below):
#!/bin/bash
<snip>
# array of build directories -- in order
declare -a blddirs
blddirs=('trinity-qt3'
'trinity-pyqt3'
'trinity-tqtinterface'
'trinity-arts'
'trinity-kdelibs'
'trinity-kdebase'
'trinity-kdevelop'
'trinity-kdewebdev')
# loop through the blddirs to build each in order
for((i=0;i<${#blddirs[@]};i++)); do
# copy your dev dir to the build dir (I don't build in my original dev dir)
# if working with srpms, you could either install them at this point and
# build with 'rpmbuild -bb specfile' or just 'rpmbuild --rebuild srpm'.
cp -a ${pbbase}/${blddirs[$i]} $bldbase
# if the dir got copied (or spec file exists) -- use it, if not skip it
if [[ -d ${bldbase}/${blddirs[$i]} ]]; then
# start time to screen & log
echo -e "\n$(date '+%b %e %T') building: ${blddirs[$i]}\n" | tee -a ${bldlog}
# change into the build dir
cd ${bldbase}/${blddirs[$i]}
# move any existing packages out to pkgdir (adjust for .rpm or .deb)
echo -e "\n Testing for old packages and moving to ${binsavdir}\n"
if ls *tar.xz &>/dev/null; then
mv -fv *tar.xz ${binsavdir} | tee -a ${bldlog}
fi
# build the new package (adjust for rpbbuild -bb or whatever deb uses)
(makepkg -s)
# install and move new package to $pkgbin dir (adjust as needed)
# if the build failed, issue warning an move on
echo -e "\n Testing for new packages, installing, and moving to ${binpkgdir}\n"
if ls *tar.xz &>/dev/null; then
sudo pacman -U --noconfirm *tar.xz | tee -a ${bldlog}
mv -fv *tar.xz ${binpkgdir} | tee -a ${bldlog}
else
echo "WARNING: Build of '${blddirs[$i]}' produced no package, skipping..."
| tee -a ${bldlog}
fi
else
echo "WARNING: Directory '${bldbase}/${blddirs[$i]}' not found - skipping" |
tee -a ${bldlog}
fi
done
exit 0
The link to the full script is:
http://www.3111skyline.com/dl/dt/trinity/arch/scr/bldtrinsvn-all.sh
It should be able to be easily adapted for rpm based builds or whatever debian
and slackware use. The PKGBUILD scripts that Arch Linux uses with "makepkg" work
the same way SPEC files work with "rpmbuild" on rpm based distros.
--
David C. Rankin, J.D.,P.E.
well, I totally screwed up my Debian Lenny install last night. I was
fighting an application error, made some bad choices, and ended up with
a non-useable system. X wouldn't work & I could not get apt/aptitude to
do anything worthwhile.
SO, 9pm last night I started the squeeze upgrade process. just about
finished it last night ( gnome login worked, but KDE was not to be
found). That was about 12:30am..
6am I was back at it.. oops, ran out of "/" file space, that sucks..
removed a bunch of useless apps.. got some space back. Installed
trinity.. fixed a few squeeze upgrade issue, and about noon today I had
my system back. My wife's desktop looks just like it did yesterday,
except it says "trinity" on the left hand side:) I doubt she will
notice. Her kmail is up & running, as is my gnome login.
# uname -a
Linux paulandcilla.homelinux.org 2.6.32-5-686 #1 SMP Wed Jan 12 04:01:41
UTC 2011 i686 GNU/Linux
too many trinity apps to list, but here's one:
ii kdepim-trinity
4:3.5.12-0debian7+r1178442 Personal Information Management
apps from the official KDE3 release
yeah!!!!!
--
Paul Cartwright
Guys,
I started the kdm greeter and it started fine on vt:07. It listed my login and
looked nice. I type my password, hit return and .. "Login Failed" Huh?
I looked though kdmrc and there didn't seem to be anything that would prevent a
user login. root wasn't allowed, but that is the default.
Anybody else seeing this? Any thoughts on why?
--
David C. Rankin, J.D.,P.E.
I installed squeeze on my Dell laptop recently. Then I went through the
trinity instructions for installing trinity KDE. Once I finished I had
no wireless and could find no way to configure it, nothing worked. It is
an Intel wireless card, 2915ABG I think. What I did was install LXDE &
ceni. logged out, logged into LXDE session, ran ceni, and configured
wireless for a static IP on my subnet. logged out & back into trinity &
wireless worked.
in trinity, when I started, all the networking tools I could find would
not configure my wireless. one did show my wireless router, but would
not let me add it or connect to it.
--
Paul Cartwright
All,
Just a note on the current svn kdewebdev build. There are a few *optional*
dependencies for quanta+ that are currently not built. They are probably
somewhere in the tree waiting for a cmake port. If not, then we might want to
add them to the 'todo' list for the 3.5.13 release. (low priority)
Reason - when you first launch quant+ you are greeted with the following list
of missing packages:
Some applications required for full functionality are missing:
- Kommander [http://kommander.kdewebdev.org] - various script based dialogs
including the Quick Start dialog will not be available;
- Tidy [http://tidy.sourceforge.net] - HTML syntax checking will not be available;
- Kompare [http://bruggie.dnsalias.org/kompare] - comparing of files by content
will not be available;
- GPG (OpenPGP) [http://www.gnupg.de] - preview browser configuration will not
be available;
- KXSLDbg [http://xsldbg.sourceforge.net/] - XSLT debugging will not be available;
- KImageMapEditor [http://www.nongnu.org/kimagemap/] - editing HTML image maps
will not be available;
- KLinkStatus [http://kde-apps.org/content/show.php?content=12318] - link
validity checking will not be available;
- Cervisia [http://www.kde.org/apps/cervisia] - CVS management plugin will not
be available.
For Arch Linux (as with most other distributions) tidy and gnupg are already
available and can simply be added as dependencies of the kdewebdev package by
the person packaging it. (note: the gpg dependency is for gnupg NOT gnupg2)
However, the following are only available as kde4 packages (at least on Arch)
- Kommander
- Kompare
- KXSLDbg
- KImageMapEditor
- KLinkStatus
- Cervisia (usually packaged as part of the kde-sdk)
Also, since cvs is somewhat outmoded by svn,git,etc.. the quanta dependency
for cervisia could just be dropped if it presents too much of a problem to
include. (at least in my opinion - others may want it)
As noted in the subject, these are OPTIONAL dependencies for quanta so they
are low on the manpower priority list, but they are certainly 'nice to have' and
convey a bit of 'polish' when they are present.
--
David C. Rankin, J.D.,P.E.
All,
In going back and forth over "this build issue/that build issue/etc...", after
running Trinity on Arch for the past day and kicking the tires, I wanted to make
sure I dropped a note letting everyone that has worked so hard on this project
know how good it works -> IT WORKS GREAT!
Great job to all, this is going to be one fantastic desktop.
--
David C. Rankin, J.D.,P.E.
Tim, Robert, Serghei, all
Is there a way to tell Trinity to ignore all the kde4 junk in
/usr/share/autostart? (other than uninstalling kde4) I say this because I just
took all my binary packages and installed them on a box with both a prior kde3
install (in /opt/kde) and a kde4 install (/usr/bin) and things were wild to say
the least.
I moved both existing ~/.kde and ~/.kde4 directories to ~/.kde-sav and
~/.kde4-sav before launching Trinity. (I forgot to delete the ksycoca from
/var/tmp though and I suspect that caused 90% of the problem)
Trinity started just fine and did the initial configuration. Then ksplash from
the old kde3 install appeared. Then akonadi/nepomuk started trying to index
everything, then the kde4 plasma-panel loaded over the Trinity kicker and all
the window decorations were gone.
I suspect Trinity was trying to pull the decorations from the old kde3 install
due to the sysconfigcache in /var/tmp (I'll try deleting that next time), but
the real issue is the kde4 autostart mess:
[21:42 supersff:/usr/share/apps/kdm/sessions] # l /usr/share/autostart/
total 128
drwxr-xr-x 2 root root 4096 Feb 10 16:53 .
drwxr-xr-x 408 root root 12288 Feb 15 11:49 ..
-rw-r--r-- 1 root root 4417 Jan 27 08:47 kaddressbookmigrator.desktop
-rw-r--r-- 1 root root 3649 Jan 27 08:46 kalarm.autostart.desktop
-rw-r--r-- 1 root root 6539 Jan 18 15:24 kgpg.desktop
-rwxr-xr-x 1 root root 11509 Jan 19 16:04 klipper.desktop
-rw-r--r-- 1 root root 4196 Jan 19 16:23 kmix_autostart.desktop
-rw-r--r-- 1 root root 6638 Jan 19 16:03 konqy_preload.desktop
-rw-r--r-- 1 root root 5846 Jan 27 08:46 korgac.desktop
-rw-r--r-- 1 root root 2881 Jan 19 16:04 krunner.desktop
-rw-r--r-- 1 root root 13602 Jan 19 16:04 kwrited-autostart.desktop
-rw-r--r-- 1 root root 10584 Jan 19 16:04 nepomukserver.desktop
-rw-r--r-- 1 root root 3710 Jan 19 16:05 plasma-desktop.desktop
-rw-r--r-- 1 root root 28 Jan 19 16:05 plasma.desktop
-rw-r--r-- 1 root root 908 Dec 9 02:51
polkit-kde-authentication-agent-1.desktop
-rw-r--r-- 1 root root 6000 Jan 18 15:24 printer-applet.desktop
-rw-r--r-- 1 root root 3506 Jan 19 16:23 restore_kmix_volumes.desktop
In order to make Trinity play nicely with an existing kde4 install, can
something be changed in the Trinity code to tell it to ignore all the kde4
autostart files?
--
David C. Rankin, J.D.,P.E.
Serghei,
Tomorrow when looking at gcc cmake issues, add amarok osd.h line 40 to the list:
/home/david/tbld/applications/amarok/amarok/src/osd.h:40:78: error: cannot call
constructor ‘QImage::QImage’ directly
/home/david/tbld/applications/amarok/amarok/src/osd.h:40:78: error: for a
function-style cast, remove the redundant ‘::QImage’
Just needs ‘::QImage’ deleted :)
Then after fixing the constructor, you will run into the following error at 82%
[ 82%] Building CXX object
amarok/src/CMakeFiles/amarok-shared.dir/organizecollectiondialog.cpp.o
cd /home/david/tbld/applications/amarok/src/amarok/src && /usr/bin/c++
-Damarok_shared_EXPORTS -DHAVE_CONFIG_H -DUSE_QT3 -DQT_NO_ASCII_CAST
-DQT_CLEAN_NAMESPACE -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION
-DQT_THREAD_SUPPORT -D_REENTRANT -march=x86-64 -mtune=generic -O2 -pipe
-include tqt.h -fPIC -I/home/david/tbld/applications/amarok/src/amarok/src
-I/home/david/tbld/applications/amarok/amarok/src
-I/home/david/tbld/applications/amarok/src
-I/home/david/tbld/applications/amarok/src/amarok/src/amarokcore
-I/home/david/tbld/applications/amarok/src/amarok/src/magnatunebrowser
-I/home/david/tbld/applications/amarok/amarok/src/amarokcore
-I/home/david/tbld/applications/amarok/amarok/src/analyzers
-I/home/david/tbld/applications/amarok/amarok/src/statusbar
-I/home/david/tbld/applications/amarok/amarok/src/plugin -I/opt/trinity/include
-I/opt/qt/include -I/opt/qt/include/tqt -I/usr/include/taglib -o
CMakeFiles/amarok-shared.dir/organizecollectiondialog.cpp.o -c
/home/david/tbld/applications/amarok/src/amarok/src/organizecollectiondialog.cpp
/home/david/tbld/applications/amarok/src/amarok/src/organizecollectiondialog.cpp:256:9:
error: prototype for ‘QString OrganizeCollectionDialog::buildDestination(const
QString&, const MetaBundle&)’ does not match any in class ‘OrganizeCollectionDialog’
/home/david/tbld/applications/amarok/src/amarok/src/organizecollectiondialog.h:59:21:
error: candidate is: virtual QString
OrganizeCollectionDialog::buildDestination(const QString&, const MetaBundle&) const
/home/david/tbld/applications/amarok/src/amarok/src/organizecollectiondialog.cpp:262:9:
error: prototype for ‘QString OrganizeCollectionDialog::buildFormatTip()’ does
not match any in class ‘OrganizeCollectionDialog’
/home/david/tbld/applications/amarok/src/amarok/src/organizecollectiondialog.h:60:21:
error: candidate is: virtual QString OrganizeCollectionDialog::buildFormatTip()
const
/home/david/tbld/applications/amarok/src/amarok/src/organizecollectiondialog.cpp:268:9:
error: prototype for ‘QString OrganizeCollectionDialog::buildFormatString()’
does not match any in class ‘OrganizeCollectionDialog’
/home/david/tbld/applications/amarok/src/amarok/src/organizecollectiondialog.h:61:21:
error: candidate is: virtual QString
OrganizeCollectionDialog::buildFormatString() const
/home/david/tbld/applications/amarok/src/amarok/src/organizecollectiondialog.cpp:279:9:
error: prototype for ‘QString OrganizeCollectionDialog::cleanPath(const
QString&)’ does not match any in class ‘OrganizeCollectionDialog’
/home/david/tbld/applications/amarok/src/amarok/src/organizecollectiondialog.h:63:21:
error: candidate is: virtual QString OrganizeCollectionDialog::cleanPath(const
QString&) const
make[2]: ***
[amarok/src/CMakeFiles/amarok-shared.dir/organizecollectiondialog.cpp.o] Error 1
make[2]: Leaving directory `/home/david/tbld/applications/amarok/src'
make[1]: *** [amarok/src/CMakeFiles/amarok-shared.dir/all] Error 2
make[1]: Leaving directory `/home/david/tbld/applications/amarok/src'
make: *** [all] Error 2
Aborting...
Dunno how to fix this one :(
--
David C. Rankin, J.D.,P.E.