Return-Path: X-Original-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4224E7095 for ; Fri, 9 Dec 2011 13:44:35 +0000 (UTC) Received: (qmail 29943 invoked by uid 500); 9 Dec 2011 13:44:34 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 29899 invoked by uid 500); 9 Dec 2011 13:44:34 -0000 Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ooo-dev@incubator.apache.org Delivered-To: mailing list ooo-dev@incubator.apache.org Received: (qmail 29891 invoked by uid 99); 9 Dec 2011 13:44:34 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Dec 2011 13:44:34 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of Mathias_Bauer@gmx.net designates 213.165.64.22 as permitted sender) Received: from [213.165.64.22] (HELO mailout-de.gmx.net) (213.165.64.22) by apache.org (qpsmtpd/0.29) with SMTP; Fri, 09 Dec 2011 13:44:27 +0000 Received: (qmail invoked by alias); 09 Dec 2011 13:44:04 -0000 Received: from pd956f467.dip0.t-ipconnect.de (EHLO [192.168.90.139]) [217.86.244.103] by mail.gmx.net (mp068) with SMTP; 09 Dec 2011 14:44:04 +0100 X-Authenticated: #17242763 X-Provags-ID: V01U2FsdGVkX18mfbEi01smkQlA90hKKp3chSlJz4sLlWnRzrEFWI JWaGa4yydVHH9b Message-ID: <4EE210A3.4010901@gmx.net> Date: Fri, 09 Dec 2011 14:44:03 +0100 From: Mathias Bauer 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> In-Reply-To: <4EE1D01D.8090604@googlemail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 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. Regards, Mathias