OK, try it again with revision 1172884 or above. Hopefully I stamped the remaining header issues in kdelibs out, but you never know....
Tried again with 1173126. tqtinterface, arts, and kdelibs built without errors. Progress!
kdebase failed to build. :( Log attached.
OK, try it again with revision 1172884 or above. Hopefully I stamped the remaining header issues in kdelibs out, but you never know....
Tried again with 1173126. tqtinterface, arts, and kdelibs built without errors. Progress!
kdebase failed to build. :( Log attached.
That is apparently due to the new Kickoff menu option. Let me do another rebuild test here and see what I can fix.
Tim
I see you merged many of the Chakra patches. Here is what I found that does not seem to be in trinity kde. Of course, you know best whether the patches should be merged.
dbus-qt3 dbus-qt3-compile-fix-thoenig-01.patch dbus-qt3-do-not-close-shared-connection-thoenig-01.patch
gtk-qt-engine fix-konqueror-flash.patch
kdebase 04-safely_remove_umount_progress_dialog.patch (seems useful; there is no feedback or progress bar when unmounting, just the icon disappearing; and the icon does not always disappear on 3.5.10) 05-transparent_lock_logout_applet.patch 08-hide_unneeded_menu_entries.patch 09-better_screen_icon_in_desktop_prefs.patch 10-disable_kpersonalizer.patch (I don't like this patch) 15-various_less_verbal_kdesu.patch 20-ksmserver_theme_support.patch 21-ksmserver_fade.patch (if merging this one please see bug 258) 22-add_change_session_icon.patch 24-startkde_source_profile_directly.patch (seems distro-specific, expects /etc/profile.d) 26-bigger_title_icons_in_kcontrol.patch fix-async_history.patch fix-kde3and4.diff (seems to be distro-specific and is looking for hard-coded directories) post-build-dunkelstern-ksmserver-theme-kcm-fix.patch (I don't know what this is) post-build-fix-zsh_profile.patch (seems distro-specific)
I hope this helps. Just ignore if you already looked at those patches!
Darrell
I see you merged many of the Chakra patches. Here is what I found that does not seem to be in trinity kde. Of course, you know best whether the patches should be merged.
dbus-qt3 dbus-qt3-compile-fix-thoenig-01.patch dbus-qt3-do-not-close-shared-connection-thoenig-01.patch
I don't provide dbus-qt3 in the Trinity source.
gtk-qt-engine fix-konqueror-flash.patch
Already applied.
My other notes are in parenthesis below:
kdebase 04-safely_remove_umount_progress_dialog.patch (seems useful; there is no feedback or progress bar when unmounting, just the icon disappearing; and the icon does not always disappear on 3.5.10) 05-transparent_lock_logout_applet.patch (duplicate functionality) 08-hide_unneeded_menu_entries.patch (why do I want to hide applications
from the users?)
09-better_screen_icon_in_desktop_prefs.patch 10-disable_kpersonalizer.patch (I don't like this patch) (me either) 15-various_less_verbal_kdesu.patch (I like to let the users know *why*
they need to enter their password)
20-ksmserver_theme_support.patch (duplicate functionality) 21-ksmserver_fade.patch (if merging this one please see bug 258)
(duplicate functionality)
22-add_change_session_icon.patch (duplicate functionality) 24-startkde_source_profile_directly.patch (seems distro-specific, expects /etc/profile.d) (yes it is) 26-bigger_title_icons_in_kcontrol.patch (big and clunky is for KDE4...) fix-async_history.patch (why? What is wrong with flushing the
configuration files directly to disk? Personally I hate it when I configure something, apply it, and the computer crashes/goes down nearly simultaneously for a different reason. Then I have to *re*-configure everything; this makes for a bad user experience)
fix-kde3and4.diff (seems to be distro-specific and is looking for hard-coded directories) (duplicate functionality) post-build-dunkelstern-ksmserver-theme-kcm-fix.patch (I don't know what this is) (distro specific) post-build-fix-zsh_profile.patch (seems distro-specific) (yes)
I hope this helps. Just ignore if you already looked at those patches!
Tim
Once again, you're way ahead of the curve. :) Seems you already looked at those patches too.
Only one you provided no comment:
04-safely_remove_umount_progress_dialog.patch
Seems that might be useful, but your decision!
Once again, you're way ahead of the curve. :) Seems you already looked at those patches too.
Only one you provided no comment:
04-safely_remove_umount_progress_dialog.patch
Seems that might be useful, but your decision!
I meant to comment on that one as well, but didn't type anything apparently.
Oops!
That one duplicates functionality as well; 3.5.11 has a progress popup that appears if the unmount takes more than half a second or so. The icon is also removed at the end of the unmount, provided HAL can disconnect the device from the system properly. At the very least, the icon changes to the unmounted version.
Tim
I have Debian Lenny installed on some separate partitions in my office system. During all of our conversations and work I had plain forgotten about that install. I have KDE 3.5.9/10 or whatever the default Debian system provides. The system is current to about April or May 2010.
Do I need to uninstall those KDE 3 packages before installing Trinity nightlies? Or will apt-get/synaptic handle the updates?
Do I need only add the Trinity PPA to the sources.list to find to install the nightlies? (Is this the correct web page?: https://launchpad.net/~kde3-maintainers/+archive/trinity-svn-nightly/+index?...)
Does apt-get or Synaptic provide a way to reduce download bandwidth by updating only the differences in packages (like rsync) rather than an entire package?
I realize these are not developer specific questions. I'm not a Debian guru or main user, but I might be able to help with some testing by installing Trinity in my Debian install.
Darrell
I have Debian Lenny installed on some separate partitions in my office system. During all of our conversations and work I had plain forgotten about that install. I have KDE 3.5.9/10 or whatever the default Debian system provides. The system is current to about April or May 2010.
Do I need to uninstall those KDE 3 packages before installing Trinity nightlies? Or will apt-get/synaptic handle the updates?
You shouldn't need to do anything fancy.
Do I need only add the Trinity PPA to the sources.list to find to install the nightlies? (Is this the correct web page?: https://launchpad.net/~kde3-maintainers/+archive/trinity-svn-nightly/+index?...)
No, that is an old Ubuntu-Lucid-only archive. All new development takes place on the internal QuickBuild system due to build time constraints on the shared Launchpad system.
I have added installation instructions to the main Trinity web page at: http://trinity.pearsoncomputing.net/
Just click on your distro and follow the instructions. ;-)
Does apt-get or Synaptic provide a way to reduce download bandwidth by updating only the differences in packages (like rsync) rather than an entire package?
Not sure, sorry. I remember some discussion about that many years ago, but I do not know if that feature ever made it in to Debian.
I realize these are not developer specific questions. I'm not a Debian guru or main user, but I might be able to help with some testing by installing Trinity in my Debian install.
Much appreciated; I already have a few Debian testers but more is always better.
Tim
Are any of your Debian testers going to test Linux Mint Debian Edition (LMDE) with Trinity? If not then perhaps put out the word to try?
Basically LMDE is Debian Testing, which should work, but I'm curious if anybody has or will perform actual tests with that version.
Darrell
Are any of your Debian testers going to test Linux Mint Debian Edition (LMDE) with Trinity? If not then perhaps put out the word to try?
Basically LMDE is Debian Testing, which should work, but I'm curious if anybody has or will perform actual tests with that version.
Darrell
Not that I'm aware of; if you would like to test it that would be great!
I have added a distribution test matrix here: http://trinity.pearsoncomputing.net/wiki/bin/view/Developers/FunctionalityTe...
When you have given it a thorough testing, add the distribution to the appropriate table along with some comments and a rating from 0 to 5.
Anyone can edit the test matrix if they would like to test a new distribution. If you are re-testing an existing distribution, add yourself to the Individual Test Results table, then average the individual ratings for the main distribution test table.
Tim
I'll give it a go, later on today URL (don't have the time to search now).
Kate
On Friday 10 September 2010, Timothy Pearson wrote:
Are any of your Debian testers going to test Linux Mint Debian Edition (LMDE) with Trinity? If not then perhaps put out the word to try?
Basically LMDE is Debian Testing, which should work, but I'm curious if anybody has or will perform actual tests with that version.
Darrell
Not that I'm aware of; if you would like to test it that would be great!
I have added a distribution test matrix here: http://trinity.pearsoncomputing.net/wiki/bin/view/Developers/FunctionalityT ests
When you have given it a thorough testing, add the distribution to the appropriate table along with some comments and a rating from 0 to 5.
Anyone can edit the test matrix if they would like to test a new distribution. If you are re-testing an existing distribution, add yourself to the Individual Test Results table, then average the individual ratings for the main distribution test table.
Tim
FTBFS. Build log attached.
First noticeable error messages:
icalformatimpl.cpp:34:28: error: libical/ical.h: No such file or directory icalformatimpl.cpp:35:34: error: libical/icalparser.h: No such file or directory icalformatimpl.cpp:36:39: error: libical/icalrestriction.h: No such file or directory
From icalformatimpl.cpp:
extern "C" { #include <libical/ical.h> #include <libical/icalparser.h> #include <libical/icalrestriction.h> }
I can't find any such directory or files on my build system. I just updated svn. All packages that have been built are installed.
Darrell
FTBFS. Build log attached.
First noticeable error messages:
icalformatimpl.cpp:34:28: error: libical/ical.h: No such file or directory icalformatimpl.cpp:35:34: error: libical/icalparser.h: No such file or directory icalformatimpl.cpp:36:39: error: libical/icalrestriction.h: No such file or directory
From icalformatimpl.cpp:
extern "C" { #include <libical/ical.h> #include <libical/icalparser.h> #include <libical/icalrestriction.h> }
I can't find any such directory or files on my build system. I just updated svn. All packages that have been built are installed.
Darrell
kdepim needs libical, available from here: http://sourceforge.net/projects/freeassociation/
It's a relatively small parser for PIM files.
You will also need libcaldav and libcarddav, both of which are available on the Trinity home page under "Related Projects".
Tim
kdepim needs libical, available from here: http://sourceforge.net/projects/freeassociation/
It's a relatively small parser for PIM files.
You will also need libcaldav and libcarddav, both of which are available on the Trinity home page under "Related Projects".
Are these new dependencies? Or options?
What benefit do they provide? For example, I have no need for most of the bling some people think they need with email. I use a very basic KMail. Do I need these added dependencies?
kdepim needs libical, available from here: http://sourceforge.net/projects/freeassociation/
It's a relatively small parser for PIM files.
You will also need libcaldav and libcarddav, both of which are available on the Trinity home page under "Related Projects".
Are these new dependencies? Or options?
What benefit do they provide? For example, I have no need for most of the bling some people think they need with email. I use a very basic KMail. Do I need these added dependencies?
A heavily patched libical was originally included as part of the kdepim source code. For the Trinity project this was split into an external dependency, as other programs also use libical and there was no more need for the KDE-specific patches to the upstream code. This is a dependency that will need to be filled even for basic functionality.
libcaldav and libcarddav are for the new CalDAV and CardDAV resources, for korganizer and kaddressbook respectively. You can disable them, but you will lose interoperability with newer PIM suites such as Google Calendar and Zimbra.
Tim
A heavily patched libical was originally included as part of the kdepim source code. For the Trinity project this was split into an external dependency, as other programs also use libical and there was no more need for the KDE-specific patches to the upstream code. This is a dependency that will need to be filled even for basic functionality.
libcaldav and libcarddav are for the new CalDAV and CardDAV resources, for korganizer and kaddressbook respectively. You can disable them, but you will lose interoperability with newer PIM suites such as Google Calendar and Zimbra.
So libical is required and is a replacement for libkcal?
What about libcaldav? libcarddav? Are there configure options to disable the latter two?
I checked configure --help and saw nothing obvious for all three. :(
I don't see the links for the libcaldav and libcarddav sources. I saw links to deb packages.
Note: Just about everything I select at your quickbuild site uses an "invalid certificate." I hate this so-called feature of Firefox. I know how to add exceptions, but would be nice if folks did not have to do that. :)
A heavily patched libical was originally included as part of the kdepim source code. For the Trinity project this was split into an external dependency, as other programs also use libical and there was no more need for the KDE-specific patches to the upstream code. This is a dependency that will need to be filled even for basic functionality.
libcaldav and libcarddav are for the new CalDAV and CardDAV resources, for korganizer and kaddressbook respectively. You can disable them, but you will lose interoperability with newer PIM suites such as Google Calendar and Zimbra.
So libical is required and is a replacement for libkcal?
Yes. It is used by libkcal though; it is a replacement for the old internal version of libical. Trust me; it's much better this way--the old integrated libical had many bugs, including random changing of Korganizer appointment times.
What about libcaldav? libcarddav? Are there configure options to disable the latter two?
The resources that use them *should* shut down automatically when those libraries are not detected. If this does not occur, let me know and I will fix it ASAP.
I checked configure --help and saw nothing obvious for all three. :(
I don't see the links for the libcaldav and libcarddav sources. I saw links to deb packages.
Look for the .tar.gz file--it is in that list somewhere.
Note: Just about everything I select at your quickbuild site uses an "invalid certificate." I hate this so-called feature of Firefox. I know how to add exceptions, but would be nice if folks did not have to do that. :)
Yes it would. However, security certificates cost money. Lots of it. Unless someone would like to donate a site-wide certificate for *.quickbuild.pearsoncomputing.net, I don't think that will change. ;-)
Tim
Yes. It is used by libkcal though; it is a replacement for the old internal version of libical. Trust me; it's much better this way--the old integrated libical had many bugs, including random changing of Korganizer appointment times.
Shouldn't libical then be in the dependencies section of svn?
Look for the .tar.gz file--it is in that list somewhere.
I'm still unclear -- are those two packages required or optional for building kdepim? If they are required, then like libical, shouldn't they be in svn/dependencies?
Yes it would. However, security certificates cost money. Lots of it. Unless someone would like to donate a site-wide certificate for *.quickbuild.pearsoncomputing.net, I don't think that will change. ;-)
I just dislike the way Firefox does not allow the option to accept the certificate. Yet Another Example of Arrogant Developers.
Yes. It is used by libkcal though; it is a replacement for the old internal version of libical. Trust me; it's much better this way--the old integrated libical had many bugs, including random changing of Korganizer appointment times.
Shouldn't libical then be in the dependencies section of svn?
No. libical is maintained upstream in a separate source control system; the Trinity project merely uses it and does not have any control over it (rather like Qt).
Look for the .tar.gz file--it is in that list somewhere.
I'm still unclear -- are those two packages required or optional for building kdepim? If they are required, then like libical, shouldn't they be in svn/dependencies?
OK, I'm going to make them both required. They are less than 150Kb each when built and add significant functionality. As these two libraries originated within the Trinity project, and are maintained by the same, I also agree that they should be placed in svn/dependencies.
I just dislike the way Firefox does not allow the option to accept the certificate. Yet Another Example of Arrogant Developers.
Yeah, I find it annoying as well. This looks like it might work (I haven't tried it yet): http://www.cs.cmu.edu/~perspectives/firefox.html
Tim
This is a list of KDE 3.5.10 core packages provided with Slackware 12.2. (Building other packages requires using third-party build scripts.) This batch is the most important.
Here is the short list of packages I haven't been able to build:
kdebindings kdemultimedia kdepim koffice
Here are the packages I can build:
arts kdelibs kdebase kdeaccessibility kdeutils kdenetwork kdeadmin kdeartwork kdegames kdetoys kdeedu kdegraphics kdesdk kdevelop kdeaddons kdewebdev k3b amarok knemo ktorrent
Still much to do, but looking better than a few days ago! Darrell
Have you had a chance to fire up a Trinity session yet to ensure that it works properly?
Nope. I was hoping to get all of the core packages built before trying.
OK, sounds like a plan. Working on kdepim now; looks like the libical API changed slightly in 0.46.
Regarding libcaldav and libcarddav, both will build with this sequence:
./autogen.sh ./configure --prefix=/usr --mandir=/usr/share/man make make install
Tim
OK, sounds like a plan. Working on kdepim now; looks like the libical API changed slightly in 0.46.
I was able to build that version here. I forget, but the README said to run some bootstrap script, which basically recreated the make and configure files and then the package compiled.
Regarding libcaldav and libcarddav, both will build with this sequence:
./autogen.sh ./configure --prefix=/usr --mandir=/usr/share/man make make install
Okay, thanks. You said you were going to merge them into svn dependencies. Will that happen soon? If so, I'll wait to create my build script.
OK, sounds like a plan. Working on kdepim now; looks like the libical API changed slightly in 0.46.
I was able to build that version here. I forget, but the README said to run some bootstrap script, which basically recreated the make and configure files and then the package compiled.
Regarding libcaldav and libcarddav, both will build with this sequence:
./autogen.sh ./configure --prefix=/usr --mandir=/usr/share/man make make install
Okay, thanks. You said you were going to merge them into svn dependencies. Will that happen soon? If so, I'll wait to create my build script.
Not sure when I'll get around to it. The build process will be exactly the same either way through.
Also, try updating kdepim to SVN revision 1174005. I have added some autoconf magic to detect libical 0.46 and compensate; let me know if the build gets any farther.
Tim
Regarding libcaldav and libcarddav, both will build with this sequence:
./autogen.sh ./configure --prefix=/usr --mandir=/usr/share/man make make install
Is there the possibility that instead of making these packages kdepim dependencies, to make them kdepim configure options? E.g., --enable-libcaldav and --enable-libcarddav, with the default being disabled?
Just seems these options should be an end-user decision.
I don't think you posted the kdemultimedia build log...would you mind sending it over?
Thanks!
Tim
This is a list of KDE 3.5.10 core packages provided with Slackware 12.2. (Building other packages requires using third-party build scripts.) This batch is the most important.
Here is the short list of packages I haven't been able to build:
kdebindings kdemultimedia kdepim koffice
Here are the packages I can build:
arts kdelibs kdebase kdeaccessibility kdeutils kdenetwork kdeadmin kdeartwork kdegames kdetoys kdeedu kdegraphics kdesdk kdevelop kdeaddons kdewebdev k3b amarok knemo ktorrent
Still much to do, but looking better than a few days ago! Darrell
Currently I have the --disable-debug option in my build script configure options.
Am I correct that if I want to send debug reports I need to change that option to --enable-debug=full?
How much does that add to building times and package sizes?
Darrell
Currently I have the --disable-debug option in my build script configure options.
Am I correct that if I want to send debug reports I need to change that option to --enable-debug=full?
Yes, when backtraces are required (e.g. for crash reports).
How much does that add to building times and package sizes?
Darrell
Build time change should be minimal, but you will end up with a large amount of debugging symbol files which will inflate the total package size significantly.
Tim
Building kdebindings
FTBFS. Build log and build script attached.
Darrell
That is apparently due to the new Kickoff menu option. Let me do another rebuild test here and see what I can fix.
Oops. My mistake! I forgot to update my kdebase build script. I was still using the temporary menutab_impl.cpp file from several days ago when we first started troubleshooting.
I hope you did not spend any time on this. :(
I'm building again right now.
-
Darrell Anderson -
Kate Draven -
Timothy Pearson