I just updated my notebook with a local repo, using aptitude
update/upgrade and that removed kpilot from my system.
I thought this procedure shouldn't remove packages. Or is kpilot not
part of Trinity anymore?
And yes I still use a pilot.
I really don't want to sound impatient or ungrateful -- I realize Trinity is
an all-volunteer project to which I don't contribute (although I would if I
had the skills). I really appreciate all the time and effort that goes into
Trinity. But I have situations that are becoming critical, and I need to
know how to plan.
I have users I've been putting off for almost 3 weeks now, as well as a
couple machines of my own with problems I can't fix, because the mirrors are
down. Every day I tell them it's still not working, but it should be "any
time now."
Surely someone (Tim?) has some idea how much longer it's likely to be? All
it takes is the upload bandwidth, the amount of data still to transfer, and
some basic math to get a good estimate. Is it going to be another hour, a
day, a week, 3 more weeks? If I can't at least find out very soon, I'm
going to have to give up on Trinity and commit to another direction.
--
PGP key: http://homestead-products.com/pubkey.htm
I'm posting this question to both the developer's and user's list. Everybody's thoughts and comments are welcomed.
Bug report 676 (http://bugs.pearsoncomputing.net/show_bug.cgi?id=676) was submitted requesting that the default window placement be changed from "Smart" to Centered. A patch was provided to make that change.
What do you think?
The configuration option for window placement is found in Control Center, Desktop, Window Behavior, Moving tab.
Please keep the conversation focused to the DEFAULT setting and not what you prefer. The default setting is used when a person uses Trinity for the first time and is still learning to use the desktop. For a default setting, keep in mind new users, users migrating from Windows, traditional window placement, user expectations, newbies, etc.
This discussion is not about the merits of either option but which is best as a default for new users.
Please --- if you don't know what the "Smart" option does, then don't speculate. :)
Thanks much for your time!
Darrell
I am a member of a local LUG (Linux User Group) here in Anchorage. We meet on
Friday niights for a hands on lab session self support etc.
One comment about bandwidth around the LUG: 'never under stimater the bandwidth of
a station wagon full of tapes' This is a paraphrase of an old saying , hence the
tape refernce?
The poin being, transfering large data sets can be accomplished by loading up
the old auto and driving them, locally, seems like you could also mail a hard
drive, USB stick somwhere in a timely fashion.
--
Peace,
Greg
Ok Guys, go easy, silly question time.
When building and installing TDE from scratch on a clean, 'X'-less
system, how do I get authentication working? I assume that TDE just
passes on the task to the underlying OS. However, having done a clean
build I don't know how to get the necessary configuration and auth bits
in place, like Pam modules, init scripts etc. When you install from
packages it's all taken care of.
I can (and will) hack about to create the above but just wondered if
there was something ready rolled.
Cheers,
Mike.
--
Every question is easy if you know the answer!
Has the complete Trinity internet environment gone down now or is it
just me?
Can't seem to access anything Trinity. I was looking for the patch sets
for libcaldav & libcarddav.
Cheers,
Mike.
--
Still can't get it from the mirror. Is there somewhere I can download it,
or can anyone email it to me?
Thanks.
--
PGP key: http://homestead-products.com/pubkey.htm
Hi All,
Having started from scratch again in my quest to build TDE on wheezy,
tdelibs is now failing to compile.
I've built and installed, from Git, as per the wiki (except that
avahi-tqt will not build) and tdelibs fails with;
..........
[ 1%] Building CXX object dcop/CMakeFiles/DCOP-shared.dir/dcopclient.cpp.o
cd /tmp/tdelibs/dcop && /usr/bin/c++ -DDCOP_shared_EXPORTS
-DHAVE_CONFIG_H -DQT_NO_ASCII_CAST -DQT_CLEAN_NAMESPACE -DQT_NO_STL
-DQT_NO_COMPAT -DQT_NO_TRANSLATION -DQT_THREAD_SUPPORT -D_REENTRANT
-include tqt.h -fPIC -I/tmp/tdelibs/dcop -I/tmp/tdelibs
-I/root/trinity/root.tde.tmp/tde.new/tde/main/tdelibs/dcop
-I/tmp/tdelibs/tdecore
-I/root/trinity/root.tde.tmp/tde.new/tde/main/tdelibs/tdecore -o
CMakeFiles/DCOP-shared.dir/dcopclient.cpp.o -c
/root/trinity/root.tde.tmp/tde.new/tde/main/tdelibs/dcop/dcopclient.cpp
In file included from
/root/trinity/root.tde.tmp/tde.new/tde/main/tdelibs/dcop/dcopclient.cpp:2285:
/tmp/tdelibs/dcop/dcopclient.moc:121: error: ISO C++ forbids declaration
of âQCStringâ with no type
/tmp/tdelibs/dcop/dcopclient.moc:121: error: expected â,â or â...â
before â&â token
/tmp/tdelibs/dcop/dcopclient.moc:121: error: prototype for âvoid
DCOPClient::applicationRegistered(int)â does not match any in class
âDCOPClientâ
/root/trinity/root.tde.tmp/tde.new/tde/main/tdelibs/dcop/dcopclient.h:745:
error: candidate is: void DCOPClient::applicationRegistered(const
TQCString&)
/tmp/tdelibs/dcop/dcopclient.moc:134: error: ISO C++ forbids declaration
of âQCStringâ with no type
/tmp/tdelibs/dcop/dcopclient.moc:134: error: expected â,â or â...â
before â&â token
/tmp/tdelibs/dcop/dcopclient.moc:134: error: prototype for âvoid
DCOPClient::applicationRemoved(int)â does not match any in class
âDCOPClientâ
/root/trinity/root.tde.tmp/tde.new/tde/main/tdelibs/dcop/dcopclient.h:754:
error: candidate is: void DCOPClient::applicationRemoved(const TQCString&)
/tmp/tdelibs/dcop/dcopclient.moc:166: error: ISO C++ forbids declaration
of âQCStringâ with no type
/tmp/tdelibs/dcop/dcopclient.moc:166: error: expected â,â or â...â
before â&â token
/tmp/tdelibs/dcop/dcopclient.moc:166: error: prototype for âvoid
DCOPClient::callBack(int, int)â does not match any in class âDCOPClientâ
/root/trinity/root.tde.tmp/tde.new/tde/main/tdelibs/dcop/dcopclient.h:794:
error: candidate is: void DCOPClient::callBack(int, const TQCString&,
const TQByteArray&)
/tmp/tdelibs/dcop/dcopclient.moc: In member function âvirtual bool
DCOPClient::qt_emit(int, TQUObject*)â:
/tmp/tdelibs/dcop/dcopclient.moc:196: error: ISO C++ forbids declaration
of âtype nameâ with no type
/tmp/tdelibs/dcop/dcopclient.moc:196: error: ISO C++ forbids declaration
of âtype nameâ with no type
/tmp/tdelibs/dcop/dcopclient.moc:196: error: expected primary-expression
before âconstâ
/tmp/tdelibs/dcop/dcopclient.moc:196: error: expected â)â before âconstâ
/tmp/tdelibs/dcop/dcopclient.moc:197: error: ISO C++ forbids declaration
of âtype nameâ with no type
/tmp/tdelibs/dcop/dcopclient.moc:197: error: ISO C++ forbids declaration
of âtype nameâ with no type
/tmp/tdelibs/dcop/dcopclient.moc:197: error: expected primary-expression
before âconstâ
/tmp/tdelibs/dcop/dcopclient.moc:197: error: expected â)â before âconstâ
/tmp/tdelibs/dcop/dcopclient.moc:200: error: ISO C++ forbids declaration
of âtype nameâ with no type
/tmp/tdelibs/dcop/dcopclient.moc:200: error: ISO C++ forbids declaration
of âtype nameâ with no type
/tmp/tdelibs/dcop/dcopclient.moc:200: error: expected primary-expression
before âconstâ
/tmp/tdelibs/dcop/dcopclient.moc:200: error: expected â)â before âconstâ
make[2]: *** [dcop/CMakeFiles/DCOP-shared.dir/dcopclient.cpp.o] Error 1
make[2]: Leaving directory `/tmp/tdelibs'
make[1]: *** [dcop/CMakeFiles/DCOP-shared.dir/all] Error 2
make[1]: Leaving directory `/tmp/tdelibs'
make: *** [all] Error 2
.........
I've then mirrored exactly what I've done on wheezy in a squeeze chroot
and the results are the same, including the failure of avahi-tqt to build.
As a matter of interest, apart from the 'util' linking issue on wheezy,
tdelibs built ok last week.
Any ideas?
Regards,
Mike.
--
I made extensive changes to the developer's page at the wiki. I ask that everybody review.
I won't pretend I got everything perfectly correct. Others with more experience need to perform a subject matter expert technical review.
I have a one sentence spot where eventually a link will be added as a gateway to package specific information about building. My hope for those pages will include unique build requirements, using extra include directories, what external packages are required to provide additional functionality, etc.
For that last point, this is not a detailed dependency list. Package managers and upstream maintainers handle those details. I am addressing additional functionality. For example, ocaml is not required to build kalzium in kdeedu, but adds additional functionality when present during building.
Please review the wiki. If uncomfortable directly editing the wiki, please forward corrections to me.
Thanks!
Darrell
