On Sun, 2008-01-06 at 18:23 +0000, Dr J A Gow wrote: > I think we may have been talking at cross-purposes. I was referring to > the proposal to copy both plugins to the OpenSync plugin directory. In > this case there will always be one of the two plugins that will be a > redundant module that should _not_ be used with the particular version > of OpenSync - but both will be visible on an msynctool --listplugins. > This would be bad.
Well, okay, the patch I just sent in this thread only installs the relevant plugin, so surely it solves your issue? It has, however, one issue: Assume someone installs this with pre-0.30 OpenSync, uses that for a while, and then upgrades OpenSync.. He will have to reinstall SyncEngine for it to detect the newer version. Is there an easy way to get around this? -- Jonny Lamb, UK [EMAIL PROTECTED] http://jonnylamb.com GPG: 0x2E039402
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. 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
