> As far as PIM syncing is concerned, I'm still happily going with the old
> multisync on my WM2003 using librra. Obviously this isn't a long term
> option, and I'd love to play with sync-engine, but it definitely still
> works.

I don't suppose you could document your setup. Just in brief if your
short on time. What versions of things and how you make it go? At the
moment i'm turning people away on IRC and saying "some day"...

> Having put a lot more thought into hal-dccm, I think it may make at
> least the connection side a lot simpler. You'll install the package and
> it will just work, particularly since for preWM5 synce-serial will
> basically have to become part of the dccm setup.

The people at #opensync and ubuntu were happy that we detect WM2003
devices based on them using the ipaq driver, rather than duplicating
the product and vendor ids in an FDI...

Though I have to strongly vote for calling it odccm 0.11 / 0.12 OR
mdccm :-P - keeping it as a new version of odccm might reduce
confusion... ?

John

-------------------------------------------------------------------------
SF.Net email is sponsored by: 
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
SynCE-Devel mailing list
SynCE-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/synce-devel

Reply via email to