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 jogischmidt@googlemail.com
 designates 209.85.215.175 as permitted sender)
Message-ID: <4EE21D50.2040307@googlemail.com>
Date: Fri, 09 Dec 2011 15:38:08 +0100
From: =?UTF-8?B?SsO8cmdlbiBTY2htaWR0?= <jogischmidt@googlemail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7;
 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>
 <B98D944A-1F4B-42DE-9EF5-E738B1EE8968@free.fr>
 <4EE1DF2A.1000005@googlemail.com> <4EE1EA02.7010003@cfl.rr.com>
 <4EE1F40E.6000902@alice.de> <4EE1FE1F.4080100@cfl.rr.com>
 <4EE204A9.2020302@googlemail.com>
In-Reply-To: <4EE204A9.2020302@googlemail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 12/9/11 1:52 PM, Oliver-Rainer Wittmann wrote:
> Hi,
>
> On 09.12.2011 13:25, TJ Frazier wrote:
>> On 12/9/2011 06:42, Herbert Duerr wrote:
>>>> You might want to test with the LilyPond extension
>>>> (OOoLilyPond-0.4.0.oxt), available on the extensions site. (As
>>>> background, think of it as the Math Engine, for writing music.) The
>>>> extension downloads and installs fine, but has problems with the update
>>>> check.
>>>
>>> Using LilyPond as a test case is a good idea, thanks!
>>>
>>>> Under 3.4Beta, the "every time" check doesn't happen (somebody fixed
>>>> it?). However, I get a crash when I try to check for updates.
>>>
>>> That crash is not related to the work on replacing the berkeleydb based
>>> extension manager,
>>
>> Surely not, since I'm running OO.o builds, with berleleydb still there.
>>
>> but on the ongoing process of replacing neon with
>>> something different.
>>
>> Was OO.o trying to replace neon as far back as 3.4Beta? If so, you're
>> probably
>> right. Otherwise, we may have two crashes.
>
> No, OOo 3.4 Beta still contains neon.
>
> I can reproduce the crash running OOo 3.4 Beta (OOO340m0) here on my
> Windows 7 system with the LilyPond extension.
> Thus, we have two crashes here:
> - One related to the LilyPond extension
> - One related to the neon not being available in AOO builds if
> --disable-copyleft configure option is used for the build.
even with --enable-copyleft

neon is removed completely and have to replaced

Juergen