Hi,
On Mon, Oct 13, 2014 at 02:46:49PM +0200, Stephan Bergmann wrote:
On 10/12/2014 03:42 PM, Sebastian Humenda wrote:
Rene Engelhard wrote:
On Sun, Oct 12, 2014 at 11:09:52AM +0100, Sebastian Humenda wrote:
I am trying to register an extension for Libreoffice. I unzipped the *.oxt-file
under /usr/lib/libreoffice/share/extensions/<extension>, but it seems not to be
recognized. Do I need to register the extension somehow or is Libreoffice
supposed to pick up all the extensions in this folder automatically? How could I
It's supposed to pick it up automatically.
The way it works in needToSyncRepository
(desktop/source/deployment/misc/dp_misc.cxx) is to compare (LO's
idea of) modification times of
/usr/lib/libreoffice/share/extensions/ directory and
~/.config/libreoffice/4/user/extensions/bundled/lastsynchronized
file. There is a dummy
/usr/lib/libreoffice/share/extensions/package.txt file specifically
intended to be manually touched whenever manually adding a bundled
extension, for platforms where the directory's modification time
would otherwise not necessarily be updated reliably, for one reason
or other.
And installing any extension via package does that (the directory):
if [ "$1" = "triggered" ]; then
for triggername in $2; do
case "$triggername" in
# new "bundled" extensions (since 3.3)
"/@OODIR@/share/extensions")
make_lo_sync_extensions
;;
esac
done
fi
where make_lo_sync_extensions is
make_lo_sync_extensions() {
touch /usr/lib/libreoffice/share/extensions
}
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.