[Cooker] Call for testing: Windows Mobile 5 / 6 devices

[Adam Williamson]

Does anyone have a Windows Mobile 5 / 6 device? If so, please help me
with some testing :)

As you may have been able to tell from my recent commits, I've been
working on improving all our packages related to communicating with
these devices, with help from Thomas B., Adam Piggz, and upstream
developers for synce and opensync.

The current status is:

We now have the appropriate modules in kernel-tmb so when you plug in a
WM5 / 6 device, the kernel stuff should all be alright (thanks Thomas).

I have fixed up a bunch of bugs and missing features in synce and
opensync packages (with some ideas from Adam Piggz) so that it works
quite smoothly with my test device (an HTC Apache running WM6). Notable
changes - fixes for an RAPI bug in sync-engine in the librapi-python and
sync-engine packages, XDG autostart files for the synce-trayicon and
synce-kpm packages so they'll be run on session start, a fix for
sync-engine failing to create a default config file if one did not
exist, building python-httplib2 so the Google Calendar opensync plugin
works, some dependency fixes, and a dbus activation file for sync-engine
so it gets run whenever something tries to access it via dbus.

I also created a set of metapackages: task-wm5sync-common ,
task-wm5sync-kde and task-wm5sync-gnome.

The overall upshot of this SHOULD be the following:

If you have a WM5/WM6 device, you can do this -

* install kernel-tmb
* install task-wm5sync-kde or task-wm5sync-gnome
* reboot (or start the 'odccm' service and either logout / login or run
synce-kpm manually)

and you should see that there's a new panel icon. This is synce-kpm. If
you plug in your phone, it should notice. You can now right click on the
icon and do various things: you can install and uninstall applications,
check device status, and check and create synchronization partnerships.

Actually synchronizing things is still slightly tricky, unfortunately -
you have to use msynctool , which is a console app. I'll provide more
details on that later. But for now I'd like people to test out the above
and let me know where it's broken. :) I'm going to find somewhere to do
a clean 2008 Spring install and test it out myself with my own device,
but external testing is always good. Thanks!
-- 
adamw