You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Brian Behlendorf <br...@organic.com> on 1998/02/04 04:05:44 UTC

autoconf decision

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

Re: autoconf decision

Posted by Randy Terbush <ra...@covalent.net>.
Brian Behlendorf <br...@organic.com> 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

I would veto any consideration to put autoconf in 1.3. 1.3 is all but
done. Some planning for how to implement it bottom up for 2.0 would be
a great project for an agressive and motivated programmer. :-)


Re: autoconf decision

Posted by Martin Kraemer <Ma...@mch.sni.de>.
On Tue, Feb 03, 1998 at 10:17:01PM -0500, Jim Jagielski wrote:
> > +1 on autoconf/autolib/automake for 2.0. 
> +1 on investigating the usefullness. If it makes
> sense, then +1. But I'm not gonna +1 "sight unseen" as it were :)

Agreed. tcsh has had both a hand-written configure AND autoconf *.in
files for a couple of releases, but of course both went different ways.
I think they finally went the autoconf way.

    Martin
-- 
| S I E M E N S |  <Ma...@mch.sni.de>  |      Siemens Nixdorf
| ------------- |   Voice: +49-89-636-46021     |  Informationssysteme AG
| N I X D O R F |   FAX:   +49-89-636-44994     |   81730 Munich, Germany
~~~~~~~~~~~~~~~~My opinions only, of course; pgp key available on request

Re: autoconf decision

Posted by Dean Gaudet <dg...@arctic.org>.
-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
>