Dr J A Gow schrieb: > On Mon, 2008-01-07 at 23:26 +0100, Vasco Steinmetz wrote: >> Still fails to compile. >> Obviously it still calls opensync_version() from synce-install-plugins.py. >> I guess the small change you made removed the plugin detection and copy part. >> >> Lines 5-10 seem superfluous now. >> > > Yes. They will probably need restructuring in some way but without > research I am not sure how setuptools needs to handle this. > > Basically what should happen now is as follows (if you can make this > happen setuptools-friendly it would be a great help :) > > In the sync-engine sources, the two plugins now reside in > sync-engine/plugins and both should be copied to the target system on > install - but held with the package and not deposited in the user's > OpenSync plugin directory (If we do this, we run the risk of losing the > plugin should the user destroy the OpenSync install for whatever reason, > and we also need OpenSync to be installed before the sync-engine). > > > Now, when the user has installed Opensync, we need to run > synce-install-plugins.py in order to copy the appropriate plugin to the > OpenSync plugin directory. Note this is a copy, not a move (as Jonny > Lamb originally suggested). This way a working copy of the plugin is > placed in the OpenSync plugins directory, but we retain a copy of all > plugins with the sync-engine install. We can run > synce-install-plugins.py automatically on the install of sync-engine if > we detect that OpenSync is already installed - but we should not make > OpenSync a dependency of sync-engine (we may support targets other than > OpenSync one day) > > Should the user then either hose their OpenSync install, or choose to > upgrade it, no plugins are lost and they do not need to reinstall > sync-engine. All they need to do is re-run synce-install-plugins.py, and > the correct plugin will be (re)inserted. > > Hope this makes sense - please ask if you need clarification. > > John. >
Well with Gentoo adding OpenSync support could be realized either by introducing a use-flag for the sync-engine package (if necessary at all) and copying the plugin file accordingly during the build (that is, outside of setup.py). Since the ebuild knows which version of OpenSync is installed it can copy the proper plugin depending on the installed OpenSync version to its correct location. Installing it on other distros (APT, RPM) may be a bit more complicated - going through setup.py would be more feasible there. Are those OpenSync plugins actually an integral part of sync-engine? There are still packages named 'synce-multisync-plugin-0.9.0' and 'libopensync-plugin-synce-0.20' in the main gentoo tree. I suppose the latter, being unmaintained and hardmasked though, provided the plugins for earlier versions of opensync. Sticking to that scheme would mean splitting/forking the opensync plugins off the sync-engine directory into a separate package, one for opensync 0.2x and one for 0.3x+ that could be downloaded/installed accordingly. I don't know anything about the dependency graph of OpenSync, sync-engine and the plugins though. Just trying to get my WM6 Hermes/TyTN/Trion/Vario synced to Kontact with KitchenSync... ;) Cheers, Vasco ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ SynCE-Devel mailing list SynCE-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synce-devel
