Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
Message-ID: <4F474C8C.5040004@apache.org>
Date: Fri, 24 Feb 2012 09:38:36 +0100
From: Herbert Duerr <hdu@apache.org>
User-Agent: generic
MIME-Version: 1.0
To: ooo-dev@incubator.apache.org
Subject: Re: Removing output trees during the bootstrap step?
References: <4F4643EF.6050503@apache.org> <4F4737F7.3030808@googlemail.com>
In-Reply-To: <4F4737F7.3030808@googlemail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

> a -1 from my side for a new default behavior of the bootstrap script.
> Make it optional, if you want, but please not the default behavior.
>
> As Armin stated the dependencies are now global.

As was pointed out in the meantime they are not really global yet.

> Thus, my trick to "workaround" the "race condition risk" is to perform a
> "build --all --deliver" before the intrinsic build is triggered in order
> to get all "new headers" delivered to the solver.

It is not only existing headers that are a problem but also generated 
headers or generated binaries, e.g. see the recent problems in
http://svn.apache.org/viewvc?view=revision&revision=1291365 or
the problem with the delzip magic interacting with an svn optimzation, 
etc. the build --all --deliver trick doesn't work reliably.

Anyway, since there is much opposition to the idea to default to a clean 
build I stop that now. I'll point to this thread though when someone 
complains about rotten binaries coming from a "build --all" or when time 
is being wasted on hunting non-reproducible problems created by these 
binaries.

Herbert