On 01/13/2011 05:49 PM, Larry Gusaas wrote:
On 2011/01/13 5:58 PM NoOp wrote:
...
I'm hesitant to install LORC3.3 until I fully understand whether or not
LORC3.3 with screw up any other Berkeley databases on my system (OOo or
otherwise). Further, does this mean that I can no longer add extensions
that use the older database, or will those be automagically converted on
install?
The Release notes for OOo 3.2.1 included the following:
http://development.openoffice.org/releases/3.2.1.html
Configuration data for extensions
The configuration data for extensions is stored in a Berkely DB which was updated to
version 4.7.25. This update contains a modified database format (for the technical
backgound see issue 100916). Due to this it it not possible to share the user configuration
with OOo 3.1.1 or older regarding extensions. This does not affect the normal user
configuration. It is recommended to backup the directory with the user installation before
installing OOo 3.2.1 and using the configuration also with older versions.
OOo 3.2.0
release notes were similar.
Since there is no 3.1.1 version of LibO it won't affect you. It only affects people who try to
revert to OOo 3.1. The database is in the users settings for LibO and will not affect OOo.
Thanks! Got it.
Gary
--
Unsubscribe instructions: E-mail to users+help@libreoffice.org
List archive: http://listarchives.libreoffice.org/www/users/
*** All posts to this list are publicly archived for eternity ***
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.