hi, now since kde 3.3 is out, it would be great to have kitchensync support in the kdeblueooth ebuild. any chance to get this in soon? thx a lot! Reproducible: Always Steps to Reproduce: 1. 2. 3.
what needs to be done?
this is what the dogs say: To enable the compilation of the konnector you have to add the "irmcsync" dir in the SUBDIR variabile of kdebluetooth/Makefile.am http://kde-bluetooth.sourceforge.net/
Hei! I'm not a "dog" :P By the way, I'll prefer that you don't enable it, because I made a lot of changes in the CVS version. This will work with a future kitchensync that will be released as a single package. Then the problem will be how to make live 2 kitchnesync (one from kdepim and this) on the same system...
Well, what's the current status concerning the kitchensync-plugin? I tried to build the kdebluetooth (from kdeextragear) from cvs against kdepim-3.3.1 or kdepim-3.3.2, but it complains about missing headers like syncee.h, etc. If I include these missing files manually from the kdepim-cvs I get: calendarthread.cpp: In constructor `KSync::CalendarThread::CalendarThread(QObject*)': calendarthread.cpp:44: error: 'class KSync::Syncee' has no member named 'setTitle' Any ideas?
The kitchensync plugin needs kdepim 3.4, for this reason it's disabled until kdepim 3.4 is out.
Is it possible to make an ebuild with irmc-support now that kde 3.4 beta is in portage?
I have to fix some things in the konnector and then I'll make a new ebuild.
I've added kdebluetooth-0.0.20050122 and kdebluetooth-0.0.20050122-r1. The "r1" is the one that enables the irmcsync konnector and for this reason it's hardmasked. You can try it with the multysink program provided with kitchensync that has a more userfriendly interface very similar to multisync, while kitchensync is more useful for debugging pourposes and advanced features. For any problem with the ebuilds please open a new bug report, while for problems with kdebluetooth and the konnector please report them to the kdebluetooth's mailing list or to the kde's bugzilla.
