Hi all,
Starting with OOo 2.0.4, OOo extensions (formerly known as "packages" or
"UNO packages") can specify dependencies on the OOo environment in which
they can be deployed. If any dependencies are not fulfilled, OOo
refuses to install the extension. See
<http://specs.openoffice.org/appwide/packagemanager/extensiondependencies1.odt>.
For OOo 2.0.4, no actual dependencies are specified, only the framework
is in place. But if you are writing a new extension that makes use of
features only available after OOo 2.0.4, you should do two things:
- Think about how this dependency could be formalized in the dependency
framework, and let me know (preferably by filing an issue for me, sb)
about it, so I can incorporate that dependency check into the package
manager code.
- Record the dependency in the extension's description.xml.
When formalizing dependencies, remember that an extension writer has to
manually record all of an extension's dependencies in its
description.xml. So, if dependencies are too fine grained, this task
becomes laborious and error prone. For example, if there is some set of
post--OOo-2.0.4 UNO API that your extension uses, it might make sense to
formulate a single dependency on that whole set of UNO API (UNO types,
services, singletons) instead of on the individual items. (In the end,
that could mean that we need to introduce only a single dependency for
OOo 2.1, namely that the extension depends on "OOo 2.1"---fine with me.)
-Stephan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
