river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dan Creswell <dan.cresw...@gmail.com>
Subject Re: build mechanisms
Date Fri, 14 Jan 2011 10:13:04 GMT
On 14 January 2011 09:54, Peter Firmstone <jini@zeus.net.au> wrote:

> Sim IJskes - QCG wrote:
>
>> On 13-01-11 12:47, Tom Hobbs wrote:
>>
>>> Personally, I feel a sense of "if it's not broken...".  I think it was
>>> Dan (but maybe not) who said that the build is the way it is because
>>> "it works".
>>>
>>
>> Exactly. Before we step into a new build system, we should first determine
>> what is actually wrong with the current build system.
>>
>> PS: The effect on me, these new build systems in the pipeline, have a
>>> paralyzing effect. I looked at the build graph of river, and saw cosmetic
>>> problem, and thought, why should i put the time in to fix it, now, to have
>>> the ant system ripped out in a months time?
>>
>>
>> Gr. Sim
>>
>>  Hang in there Sim, the benefits will become more apparent once it's
> completed, we have to bake the cake before you can taste it.
>
>
We're going to do this work in a branch right?

I may be misunderstanding but I'm not real keen on rebuilding the build
system on the basis that "it really will be better, really, even though we
can't explain why in advance" - that is the mistake of many a dev team over
the years.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message