Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of orwittmann@googlemail.com
 designates 74.125.83.47 as permitted sender)
Message-ID: <4EE214F8.5060108@googlemail.com>
Date: Fri, 09 Dec 2011 15:02:32 +0100
From: Oliver-Rainer Wittmann <orwittmann@googlemail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: ooo-dev@incubator.apache.org
Subject: Re: replace and removal of Berkeley DB
References: <4EE0DE0F.3040704@googlemail.com>
 <9FDEF96D-AF72-4BD7-8C8C-EFE07CB8D515@free.fr>
 <4EE0E8F2.9020304@googlemail.com>
 <4BEE553A-5FCE-4CC2-A76E-BD2A7E380FB6@free.fr>
 <4EE1D01D.8090604@googlemail.com> <4EE210A3.4010901@gmx.net>
In-Reply-To: <4EE210A3.4010901@gmx.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Hi Mathias,

On 09.12.2011 14:44, Mathias Bauer wrote:
> Hi Oliver,
>
> On 09.12.2011 10:08, Oliver-Rainer Wittmann wrote:
>> Hi Eric,
>>
>> thanks for the feedback.
>>
>> You are right and I forgot to mention it:
>> - The installed extensions using a user configuration of a former
>> installation will not work as the data files for the extension
>> management as changed.
>> Thus, I am proposing not to reuse a former user configuration.
>
> That would be an exaggeration. Instead of re-using it you could migrate it,
> leaving extensions out. As we will want to change the name of the profile we
> will have to migrate anyway.
>
> There is a migration service somewhere in the desktop module that gets the
> information about what should be migrated (copying files, configuration entries,
> etc.) from a configuration file. For everything that can't be migrated in this
> very simple way it also allows to implement plugable services that migrate
> particular parts of a user profile. Which services should be executed is part of
> the configuration. One of these services that already exists in the OOo source
> code is a service to migrate extensions. Just leaving this service out in a
> migration should be enough.
>

My advice/proposal was meant for developer builds.

If we want to include an migration of former OOo user configurations 
automatically or by user choice in our release is not yet been decided as far as 
I know.

Best regards, Oliver.