Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
MIME-Version: 1.0
In-Reply-To: <1343340590.11815.YahooMailClassic@web113518.mail.gq1.yahoo.com>
References: <5010F93D.5020209@googlemail.com>
	<1343340590.11815.YahooMailClassic@web113518.mail.gq1.yahoo.com>
Date: Thu, 26 Jul 2012 18:17:27 -0400
Message-ID: 
 <CAP-ksoi3PyfLv5gDGGefskcUNJFkragG-p1XvKvX0sqpKBEuKQ@mail.gmail.com>
Subject: Re: [RELEAASE][3.4.1]: propose the next build for 3.4.1 based on
 revision 1364583
From: Rob Weir <robweir@apache.org>
To: ooo-dev@incubator.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Thu, Jul 26, 2012 at 6:09 PM, Pedro Giffuni <pfg@apache.org> wrote:
> Hello guys;
> Just wondering ..
> Can I chop the Python-2.6.1 src tarball now? I left it around to make
> sure I don't break anything but it shouldn't be needed in trunk anymore.

The AOO 3.4.0 source tarballs rely on the trunk's ext-src, right?

So maybe we should wait for AOO 3.4.1 to be officially released first.
 That way we can always point developers to a working source
distribution.

-Rob


> Pedro.
>
> --- Gio 26/7/12, J=C3=BCrgen Schmidt <jogischmidt@googlemail.com> ha scri=
tto:
>
>
> not with the Hunspell update but indirectly by the integration of the
> new download mechanism. The file is new on the branch and included
> changes for these version updates that were already done on the trunk.
> Important for me to understand where it comes from to avoid such things
> in the future ...
>
> Thanks Ariel for detecting it, I would probably have stumbled over it
> when I would have tested the source release package which is on my plan
> for this week.
>
> Juergen
>
>>
>> I am currently building a new MacOS and Windows version based on
>> revision 1365887
>>
>> @Ariel: can you please build the Linux versions based on this revision
>>
>> Juergen
>>
>