Comment 16 for bug 448285

> I agree with Ted's assessment (comment #4) in the thread. This is
> really just a packaging issue, and the only real problem that I see will
> be for anyone writing new extensions on platform A, only to discover
> that they do not work on platform B or C.

that was my point I apparently failed to communicate ;-)

Packaging needs coordination and extension developers need an up-to-date
resource that informs about the status of the default installations on
platforms for which Inkscape.org provides packages on sf.net. From there
it's the developer's decision whether he accommodates to the common
minimum versions or provides installation instructions where needed.

For me it's unclear how to address packaging coordination. I know Chris
Morgan has provided the recent win32 builds and Micheal Wybrow updates
the osx packages. These processes seem independent - yet they would need
to figure out if common minimum module versions for all supported os and
python versions exists.

The Wiki Extensions category
<http://wiki.inkscape.org/wiki/index.php/Category:Extensions>
and Extension repository
<http://wiki.inkscape.org/wiki/index.php/Extension_repository>
could provide an updated extension central for developers.