On Fri, Feb 08, 2008 at 12:10:42PM +0000, Mark Ellis wrote: > Hi All Hi Mark.
> I'm currently attempting exactly what it says in the subject, and > starting to bleed out my ears. > > Please bear in mind when I ask silly questions that, being a sad and > backwards legacy user, this is the first time I've had a look at this > beast. > > The good news is, I've got sync-engine itself to install and run nicely > in its own package. Of course I have no idea whether it works properly > at the moment :) You might want to take a look at this: http://git.jonnylamb.com/?p=packaging/synce-sync-engine.git;a=summary > Now, where should the thrice cursed plugin live on a debian system, > anybody know ? I would guess it's the same on Ubuntu as well. I've > tried /usr/lib/opensync/plugins, python-plugins in that dir, the > equivalent for 0.3x when I upgraded, and a vast number of other > combinations that I can't remember. In all of these, msynctool > --listplugins doesn't see it. > > Preempting responses, yes I've been using the msynctool and plugin that > match the libopensync version I have installed each time, and the > appropriate opensync-python package is installed. A pretty way of finding out where the plugin folder is using: % pkg-config opensync-1.0 --variable=plugindir Of course, this assumes the -dev package is installed. > On a different tack, the old wiki page dealing with sync-engine > specified opensync >= 0.21. Is this definitely the case, anyone tested > an earlier one ? Debian unfortunately has 0.19 in stable and 0.35 in > experimental. Well, there's a bit of an issue with this, as you've discovered. I got talking to Michael Banck (the OS maintainer in Debian) and he told me that they didn't bother packaging 0.2x for Debian as it wasn't going to be around for long, and it had major API changes that weren't going to stay around. This is the reason 0.19 is in unstable. 0.3x is in experimental because OpenSync recommends it (check out the OS homepage for evidence of this). I was also told that 0.19 does not support python plugins, which would render the only version of OS available for use in Debian the one in experimental: 0.35. I have been getting the same issue as you with my package using the experimental OS version though. I'm not sure why it's not picking up the plugin. I need to experiment more, but have been a little busy recently. Hopefully I will have some time this weekend to sort it out. Hopefully this is a little help. Kind regards, -- Jonny Lamb, UK [EMAIL PROTECTED] http://jonnylamb.com GPG: 0x2E039402
signature.asc
Description: Digital signature
------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________ SynCE-Devel mailing list SynCE-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synce-devel
