From owner-freebsd-questions@FreeBSD.ORG Tue Feb 28 04:17:28 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 31A4C16A420 for ; Tue, 28 Feb 2006 04:17:28 +0000 (GMT) (envelope-from micahjon@ywave.com) Received: from relay3.av-mx.com (relay3.av-mx.com [137.118.16.123]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC51343D48 for ; Tue, 28 Feb 2006 04:17:27 +0000 (GMT) (envelope-from micahjon@ywave.com) X-Virus-Scan-Time: 0 Received: from [137.118.16.60] (HELO mx2.av-mx.com) by relay3.av-mx.com (CommuniGate Pro SMTP 4.2.10) with SMTP id 193656148 for freebsd-questions@freebsd.org; Mon, 27 Feb 2006 23:17:24 -0500 Received: (qmail 3356 invoked from network); 28 Feb 2006 04:17:24 -0000 Received: from dsl29042.ywave.com (HELO ?192.168.1.65?) (micahjon@ywave.com@216.227.116.42) by 0 with SMTP; 28 Feb 2006 04:17:24 -0000 X-CLIENT-IP: 216.227.116.42 X-CLIENT-HOST: dsl29042.ywave.com Message-ID: <4403CED1.70606@ywave.com> Date: Mon, 27 Feb 2006 20:17:21 -0800 From: Micah User-Agent: Thunderbird 1.5 (X11/20060113) MIME-Version: 1.0 To: Steve Lake References: <5.2.0.9.2.20060227222550.00bdb3c0@192.168.0.25> In-Reply-To: <5.2.0.9.2.20060227222550.00bdb3c0@192.168.0.25> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: A reason for major ports update? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Feb 2006 04:17:28 -0000 Steve Lake wrote: > Ok, call me the curious cat, but I just cvsupped my ports tonight > looking for a patch to Xine to fix a problem with MKV playback under KDE > 3.5 and got quite the shocker. There were about 101 ports that said > they needed to be upgraded. The part that's the kicker is I just > upgraded everything about 3 weeks ago. Did I miss something or did > something big come down the pipe that caused a major number of ports to > be updated? Or is this just coincidence? Just curious. > As was already pointed out, libtool has changed/updated. For future reference, /usr/ports/UPDATING and http://www.freshports.org are good places to check when you see massive updates like this. This one is, in fact, explained in UPDATING. Since libtool is a build dependency you're probably safe not upgrading everything unless you're like me and depend on portversion/pkg_version to tell you when things need updating. Later, Micah