Archers, All,
Currently, Arch installs trinity to /opt/trinity. Personally, I would like to
move the default install to /opt/tde. Two reasons: (1) most important -- less
typing; (2) the tradition of the install being in /opt/kde, why not standardize
around /opt/tde?
For the rest of the community -- Where are you putting tde? It would just make
sense to set a community-wide standard. Yes, I know that the location is
irrelevant and can be obtained by the standard environment files, but we
recently had a rebuild of 3.5.12 that moved from /opt/kde to /opt/kde3. That's
fine, but depending upon the repo you hit to pull files from, your system would
break due to install location differences in the various packages.
I don't have any hard feelings either way for any single location, but if it
is all the same, then if possible, I would like to see a standard that all
packagers could reference. Of course you don't have to use it, but if there is a
standard install, the balance of builds will migrate to it over time.
What says the team?
/opt/trinity
/opt/tde
/opt/tde_ver (ver being a 2 or 3-digit version: eg. 13 or 313)
/opt/other_suggestions?
Personally for me, /opt/tde works :)
(/opt/trinity is probably my fault on arch anyway :)
--
David C. Rankin, J.D.,P.E.
Calvin, Pawel, Baho,
Comparing my old tdelibs build with the current, I have -DWITH_PAM=ON. That
isn't set in the current build scripts. Is it already set by default or was
there another reason for not keeping that option?
--
David C. Rankin, J.D.,P.E.
Archers,
In the current tdelibs pkgbuild, I have run into a few questions (previously
posted). The current questions is why are we installing to provide 'kdelibs3'? Eg:
provides=('kdelibs3')
I have updated it to also register providing 'tdelibs' so that it can be
transitioned:
provides=('kdelibs3' 'tdelibs')
Other changes: pkgname=trinity-tdelibs and cmake ${srcdir}/tdelibs for the build.
Does this just need to be reworked here, or are all of the build scripts going
to have to be revised to incorporate the name changes? The name change is the
simple part, but do we know if any of the patches or supporting files also have
the 'kde...' stuff hardcoded? I'm fixing them as I come across them. If there is
any reason not to, please let me know.
--
David C. Rankin, J.D.,P.E.
Calvin, Baho, Pawel,
Why do we need 'libutempter'? I've never heard of it before. I don't mind
having an AUR package, but if we ever hope to have TDE picked up by Arch, it
needs to build on Arch. Do we really need libutempter?
--
David C. Rankin, J.D.,P.E.
Hi,
I noticed that TDE on Debian depends on GPG 1.4.10, but 2.0.14 is in their repos. This has my a little confused, since my key works perfectly in both versions, as does my friend's (his key was created in TDE's KGPG and was successfully imported into the latest Gpg4Win, which uses GPG 2.0.17). Also, I used both versions of GPG from the command line a couple of times, and the commands seem to be the same.
Is there any particular reason TDE uses an older version?
--
Kris Gamrat
Ark Linux webmaster
http://www.arklinux.org/
Tim, All,
After working through the build script for arch, I experience a tdelibs build
failure related to dcop:
Scanning dependencies of target DCOP-shared
[ 1%] Building CXX object dcop/CMakeFiles/DCOP-shared.dir/dcopstub.cpp.o
[ 1%] Building CXX object dcop/CMakeFiles/DCOP-shared.dir/dcopref.cpp.o
[ 1%] Building CXX object dcop/CMakeFiles/DCOP-shared.dir/dcopobject.cpp.o
[ 1%] Building CXX object dcop/CMakeFiles/DCOP-shared.dir/dcopclient.cpp.o
/build/src/tdelibs/dcop/dcopclient.cpp: In member function 'bool
DCOPClient::attachInternal(bool)':
/build/src/tdelibs/dcop/dcopclient.cpp:785:24: error: 'qint64' was not declared
in this scope
/build/src/tdelibs/dcop/dcopclient.cpp:785:24: error: expected ')' before
numeric constant
/build/src/tdelibs/dcop/dcopclient.cpp:785:55: error: expected ')' before ';' token
make[2]: *** [dcop/CMakeFiles/DCOP-shared.dir/dcopclient.cpp.o] Error 1
make[1]: *** [dcop/CMakeFiles/DCOP-shared.dir/all] Error 2
make: *** [all] Error 2
Any ideas? Anything else I can send to help out?
--
David C. Rankin, J.D.,P.E.
Question for those who are familiar with Python.
I always wanted Devede to run with qt3. I'm looking at the sources for Devede and see that the bulk of the app is python scripts. The dependencies listed on the Devede home page:
Mplayer, Mencoder, FFMpeg, DVDAuthor, VCDImager, MKisofs, Python, PyGTK and PyGlade.
The graphical interface is through PyGTK and PyGlade. All of the various interface dialogs are UI files, which are XML files.
How challenging would porting Devede to qt3 be?
Darrell