> > Yes, I understand that there were lots of API changes between OpenSync > > versions. I'm wondering about how to encode _our_ version number as > > well. Isn't it certainly possible that our opensync 0.3x plugin can > > change between 0.10 and 0.11, or between 0.11 and 0.12? > > It will undoubtedly, but then why do we need to encode our version > number in the plugin file any more than we do in any of the other > components of sync-engine?
Not in the plugin file - the version number would be in the ebuild file name. -- Richard Alimi Department of Computer Science Yale University ------------------------------------------------------------------------- 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
