Return-Path: 
 <dev-return-3039-apmail-apr-dev-archive=apr.apache.org@apr.apache.org>
Delivered-To: apmail-apr-dev-archive@apr.apache.org
Received: (qmail 72392 invoked by uid 500); 6 Jul 2001 10:23:11 -0000
Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
List-Post: <mailto:dev@apr.apache.org>
List-Help: <mailto:dev-help@apr.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@apr.apache.org>
List-Subscribe: <mailto:dev-subscribe@apr.apache.org>
Delivered-To: mailing list dev@apr.apache.org
Received: (qmail 72353 invoked from network); 6 Jul 2001 10:23:06 -0000
Date: Fri, 6 Jul 2001 12:22:25 +0200 (MEST)
From: Sascha Schumann <sascha@schumann.cx>
X-X-Sender: <sas@rossini.schumann.cx>
To: Justin Erenkrantz <jerenkrantz@ebuilt.com>
Cc: Mo DeJong <mdejong@cygnus.com>, <dev@apr.apache.org>
Subject: Re: Upgrading apr to autoconf 2.50 and libtool 1.4
In-Reply-To: <20010706031242.X7717@ebuilt.com>
Message-ID: <Pine.LNX.4.33.0107061220410.5945-100000@rossini.schumann.cx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N

> Wouldn't this would require EVERY single APR developer to upgrade
> to autoconf 2.50?  Yuck.  -- justin

    Additionally to that, using autoconf 2.50 is not encouraged
    as it still produces unportable shell code in some cases.
    For details, refer to the mailing list archive of new-httpd.
    In my humble opinion, we need to give it some time to
    stabilize before upgrading.

    - Sascha                                     Experience IRCG
      http://schumann.cx/                http://schumann.cx/ircg