Hi,
On Sun, Oct 12, 2014 at 02:42:15PM +0100, Sebastian Humenda wrote:
It's supposed to pick it up automatically.
get debugging information if Libreoffice didn't pick up the extension for some
reason?
What does unopkg list --bundled (or validate --bundled) say. Does it appear
$ unopkg list --bundled
All deployed bundled extensions:
<none>
And validate --bundled?
If also not, it probably isn't seen at all...
Searching the web, I was not able to find information about which files are
relevant for this recognition process at all, only about how to invoke unopkg
with an OXT extension.
Yeah, because this is supposed to be only used for "bundled" extensions.
Users shouldn't/can't "bundle" extensions with LO ;-)
Does it have a proper description.xml? (And or META-INF/manifest.xml)?
But when that isn't present a unopkg add .oxt shouldn't have worked either.
Does that work?
Regards,
Rene
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.