From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5888 invoked by alias); 5 Dec 2002 18:10:39 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 5869 invoked from network); 5 Dec 2002 18:10:37 -0000 Received: from unknown (HELO delta.ds2.pg.gda.pl) (213.192.72.1) by sources.redhat.com with SMTP; 5 Dec 2002 18:10:37 -0000 Received: from localhost by delta.ds2.pg.gda.pl (8.9.3/8.9.3) with SMTP id TAA07433; Thu, 5 Dec 2002 19:10:29 +0100 (MET) Date: Thu, 05 Dec 2002 10:10:00 -0000 From: "Maciej W. Rozycki" To: Klee Dienes cc: Daniel Jacobowitz , DJ Delorie , ac131313@redhat.com, binutils@sources.redhat.com, gdb-patches@sources.redhat.com Subject: Re: [RFC] Update to current automake/autoconf/libtool versions. In-Reply-To: Message-ID: Organization: Technical University of Gdansk MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2002-12/txt/msg00158.txt.bz2 On Thu, 5 Dec 2002, Klee Dienes wrote: > The idea here is that it's relatively straightforward for a > binutils/gdb maintainer to know what to do when updating a > configuration file (get the most recent version of the tools from the > FSF and use them), and that we have a natural tendency to stay > up-to-date with automake/autoconf changes, without having flag-day > style upgrades become an issue. That would be the most acceptable approach to me. Of the tools involved, only autoconf changed significantly recently with its transition from 2.13 to 2.50. But versions 2.5x are around long enough now to get more or less stabilized, so hesitating from going forward and making an upgrade can only impede development. -- + Maciej W. Rozycki, Technical University of Gdansk, Poland + +--------------------------------------------------------------+ + e-mail: macro@ds2.pg.gda.pl, PGP key available +