-1 on autoconf on 1.2, 1.2 is the stable release and switching to autoconf
is not a stable thing to do.
-1 on autoconf on 1.3, we're trying to get 1.3 out the door, and switching
to autoconf is not going to help that process.
+1 on autoconf/autolib/automake for 2.0.
Dean
On Tue, 3 Feb 1998, Brian Behlendorf wrote:
> At 09:38 PM 2/3/98 -0500, Cristian Gafton wrote:
> >And as with any flame wars, it this autoconf debate will degenerate into
> >an OS war if you - the apache project members - don't take a vote and
> >settle this for good.
>
> OK. It sounds like the consensus is that autoconf is too much work for
> 1.2, probably too much work for 1.3, but a possibility for 2.0. So, I've
> made a change to the apache-2.0/STATUS file.
>
> By "too much work", I don't just mean doing the legwork of replacing it
> (which it appears Cristian is more than willing to help us with). I mean
> the legwork of making sure it works on all the platforms that 1.3* up to
> this point has worked on. Introducing it at 1.3 is doable, but it could
> add a few months to the release and certainly 2 or 3 more beta cycles, imo.
>
> Brian
>
>
> --=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--
> specialization is for insects brian@organic.com
>
|