Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <4FEC4010.70001@apache.org>
Date: Thu, 28 Jun 2012 13:29:20 +0200
From: Andrea Pescetti <pescetti@apache.org>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
 rv:1.9.2.24) Gecko/20111108 Fedora/3.1.16-1.fc14 Thunderbird/3.1.16
MIME-Version: 1.0
To: ooo-dev@incubator.apache.org
Subject: Re: [RELEASE] [3.4.1] Bug 119229 as blocker (download new versions
 of extensions)
References: <4FE7247E.7070703@apache.org> <4FE82AB8.3070102@googlemail.com>
In-Reply-To: <4FE82AB8.3070102@googlemail.com>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: quoted-printable

On 25/06/2012 J=FCrgen Schmidt wrote:
> On 6/24/12 4:30 PM, Andrea Pescetti wrote:
>> This bug only affects the build infrastructure, but I propose it as a
>> blocker for 3.4.1:
>> https://issues.apache.org/ooo/show_bug.cgi?id=3D119229
>> Unless the build process starts completely clean (and it didn't as of
>> the 3.4.0 builds), the build would reuse an older, cached, version of
>> the extension even if a newer one was specified in extensions.lst
> I can see a benefit for the source release but not very critical. But
> don't see the demand for our binary release because we can easy check i=
t.

If the build system has been improved and binary builds provided by the=20
project are now fine (in OpenOffice 3.4.0 the build system did not=20
cleanup previously downloaded extensions, resulting in the Spanish and=20
Italian dictionaries not being updated), it's of course OK for me. What=20
I'd like to ensure is just that this doesn't happen with the current=20
build process, otherwise it might be better to backport the fix.

> If somebody volunteers to include, built and test it for 3.4.1 then I
> would support it.
> Any volunteer?

I might have a look, but only in the pre-build phase (which should be=20
enough: you don't need to fully build the office to check what version=20
of the extension is downloaded).

Regards,
   Andrea.