From owner-freebsd-questions@FreeBSD.ORG Thu Apr 7 06:20:03 2005 Return-Path: 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 24F6216A4CE for ; Thu, 7 Apr 2005 06:20:03 +0000 (GMT) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA64043D31 for ; Thu, 7 Apr 2005 06:20:02 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id 521CA5E64; Thu, 7 Apr 2005 02:20:02 -0400 (EDT) Received: from pi.codefab.com ([127.0.0.1]) by localhost (pi.codefab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 49934-09; Thu, 7 Apr 2005 02:20:00 -0400 (EDT) Received: from [192.168.1.3] (pool-68-161-53-96.ny325.east.verizon.net [68.161.53.96]) by pi.codefab.com (Postfix) with ESMTP id 0A8EF5DD7; Thu, 7 Apr 2005 02:19:59 -0400 (EDT) Message-ID: <4254D0B8.1060303@mac.com> Date: Thu, 07 Apr 2005 02:18:32 -0400 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050319 X-Accept-Language: en-us, en MIME-Version: 1.0 To: sergei@gnezdov.net References: <20050407041259.GA69275@xor.obsecurity.org> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at codefab.com cc: freebsd-questions@freebsd.org Subject: Re: What's the definition of the stale port? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Apr 2005 06:20:03 -0000 Sergei Gnezdov wrote: > On 2005-04-07, Kris Kennaway wrote: [ ... ] >>> How do I end up having stale ports? >> >> As time marches on :-) > > I am guessing, that port becomes stale after running cvsup. When a new version of a port is committed, anyone running the older version has a stale version. Whether you run cvsup or not doesn't affect whether a new version is available, but you are a lot more likely to notice dependency issues after running cvsup. > So, what exactly are we supposed to accomplish in respect to stale > ports, when we run pkgdb -F (deinstall, some kind of fix, simple > ignore)? pkgdb tries to update the dependencies when new versions of a port appear. Running pkgdb by itself is not especially useful, although you can check and rebuild updated ports by hand. Consider portupgrade instead.... -- -Chuck