s9y/additional_plugins — comment on commit ebe4ea94447ab4085cbd8c374b09848482ac3847
File:  line 0
By garvinhicking:

We now have s9y 1.7 in progress and it might take 3 months or 4 or 6 or 12 to release 1.7 final. That would mean no one could use the plugin properly until a new s9y core is released. That's not realistic, so a plugin needs to be able to act on its own, if it's a spartacus plugin.

I don't think that a plugin should interfer with what is kept in bundled-libs (also because we did never enforce write privileges to 'bundled-libs').

I think we should make the XML-RPC plugin work apart from what is in the core, so update XML-RPC PEAR in the plugin is okay, and it should also be the preference for the plugin. As for the core, if there's a new XML-RPC version we could/should update it in the core as well (keep possible manual changes according to the BUNDLED_NOTICE intact). It is a bit redundant, but this is the most pragmatic way to deal with it without creating problems for any type of user...?