From owner-freebsd-ports@FreeBSD.ORG Sat May 15 05:11:19 2004 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6C32916A4CE; Sat, 15 May 2004 05:11:19 -0700 (PDT) Received: from fillmore.dyndns.org (port-212-202-49-130.reverse.qsc.de [212.202.49.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id E664643D45; Sat, 15 May 2004 05:11:18 -0700 (PDT) (envelope-from eikemeier@fillmore-labs.com) Received: from [172.16.0.2] (helo=fillmore-labs.com) by fillmore.dyndns.org with esmtp (Exim 4.34; FreeBSD) id 1BOy0Z-000PMr-8f; Sat, 15 May 2004 14:11:18 +0200 Message-ID: <40A608E1.9030504@fillmore-labs.com> Date: Sat, 15 May 2004 14:11:13 +0200 From: Oliver Eikemeier Organization: Fillmore Labs GmbH - http://www.fillmore-labs.com/ MIME-Version: 1.0 To: Michael Nottebrock References: <200405150337.i4F3bMhH069783@quark.rcs.purdue.edu> <044901c43a6d$f4299a70$7890a8c0@dyndns.org> <200405151340.44395.michaelnottebrock@gmx.net> In-Reply-To: <200405151340.44395.michaelnottebrock@gmx.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit User-Agent: KMail/1.5.9 cc: Cyrille Lefevre cc: linimon@freebsd.org cc: freebsd-ports@freebsd.org Subject: Re: devel/automake14 [was: FreeBSD ports which are currentlyscheduled for deletion] X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-ports@freebsd.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 May 2004 12:11:19 -0000 Michael Nottebrock wrote: > On Saturday 15 May 2004 13:15, Cyrille Lefevre wrote: > >>I suppose a version bump is needed somewhere ? > > I believe the new automake/conf ports are still stuck in testing on the exp > cluster. The 'legacy' versions of automake/autoconf have recently been > updated to the latest releases from their respective branches, so there's no > point in rushing things, also see the expiration date. ;-) Ahem, I guess the you could interpret the original question as: where is the point of telling people to use automake18 (and setting an expiration date), if this doesn't work? Telling them the current tools suck, but the new ones are not stable (or not available at all) will only drive developers away from using them. my 2 eurocent. -Oliver