From owner-freebsd-ports@FreeBSD.ORG Fri Oct 5 00:09:24 2007 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 535FA16A419 for ; Fri, 5 Oct 2007 00:09:24 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with SMTP id C5F0E13C506 for ; Fri, 5 Oct 2007 00:09:23 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 11767 invoked by uid 399); 5 Oct 2007 00:09:17 -0000 Received: from localhost (HELO slave.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTP; 5 Oct 2007 00:09:17 -0000 X-Originating-IP: 127.0.0.1 Date: Thu, 4 Oct 2007 17:09:08 -0700 (PDT) From: Doug Barton To: Jan Henrik Sylvester In-Reply-To: <47021CA9.5030105@janh.de> Message-ID: References: <47021CA9.5030105@janh.de> X-message-flag: Outlook -- Not just for spreading viruses anymore! X-OpenPGP-Key-ID: 0xD5B2F0FB Organization: http://www.FreeBSD.org/ MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: ports-list freebsd Subject: Re: autoconf removal / Build error: KDE requires autoconf 2.53 or newer (kmastermind) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Oct 2007 00:09:24 -0000 Since no one else responded I'll take a crack ... On Tue, 2 Oct 2007, Jan Henrik Sylvester wrote: > portupgrade kmastermind-2.2_1 to kmastermind-2.2_2 failed: > > *** AUTOCONF NOT FOUND!. > *** KDE requires autoconf 2.53 or newer > > What should I do about it? > > Moreover, portupgrade does not deal with this: > > autoconf-2.53_4 < needs updating (port has 2.61_2) > autoconf-2.59_3 < needs updating (port has 2.61_2) > autoconf-2.61_2 = up-to-date with port If I can put in a plug for portmaster here, it handles this situation transparently due to supporting the entries in the MOVED file. > /usr/ports/UPDATING has no instructions what to do with the obsolete autoconf > versions. Shall I remove them although autotools-20070905, kde-3.5.7, and > kdevelop-3.4.1_2 still "require" them? Can I do that without rebuilding > kdevelop? Yes to "you should remove them," not sure about kdevelop. My gut feeling is that it would be ok to pkg_delete -f them, and then rebuild kdevelop later if you have to. Good luck, Doug -- This .signature sanitized for your protection