From owner-freebsd-questions@FreeBSD.ORG Fri Aug 29 14:15:18 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4484AB89 for ; Fri, 29 Aug 2014 14:15:18 +0000 (UTC) Received: from fly.hiwaay.net (fly.hiwaay.net [216.180.54.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D1469127F for ; Fri, 29 Aug 2014 14:15:17 +0000 (UTC) Received: from [192.168.0.27] (rbn1-216-180-19-81.adsl.hiwaay.net [216.180.19.81]) (authenticated bits=0) by fly.hiwaay.net (8.13.8/8.13.8/fly) with ESMTP id s7TEFDEB001554 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Fri, 29 Aug 2014 09:15:14 -0500 Message-ID: <54008C68.4020601@hiwaay.net> Date: Fri, 29 Aug 2014 09:21:28 -0500 From: "William A. Mahaffey III" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: "FreeBSD Questions !!!!" Subject: Re: Ports question .... References: <53FF8675.2070009@hiwaay.net> <20140828225153.GA8923@slackbox.erewhon.home> <54006B57.8070703@hiwaay.net> <54006DD8.9090200@qeng-ho.org> <54007189.8070807@hiwaay.net> <540076CD.6000201@qeng-ho.org> <5400793A.4090702@hiwaay.net> <540083EB.5020801@qeng-ho.org> In-Reply-To: <540083EB.5020801@qeng-ho.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Aug 2014 14:15:18 -0000 On 08/29/14 08:45, Arthur Chance wrote: > On 29/08/2014 13:59, William A. Mahaffey III wrote: > [huge snip] > >> I have been using portsnap, I just couldn't figure out how to get it to >> tell me what ports had been updated since I last fetched (w/o fetching >> again) .... > > It's my experience that you don't want to be told which ports have > been updated, as most updates are to ports you're not the slightest > bit interested in. There are nearly 25,000 ports according to > FreshPorts and I personally have only about 400 installed on my > desktop machine (and far fewer on my servers). That means on average > I'm totally uninterested in 98+% of all port updates. > > What you need to know is what *installed* ports are out of date with > respect to the new ports tree. That's where the 400.status-pkg > periodic script is useful. I update my ports tree via a crontab entry > at 23:00 on Fridays, and the weekly periodic script runs at 4:15 on > Saturday, so I get mail every Saturday morning telling me which > installed ports are out of date. > You are 100% correct, & I thought that was/is what I have been asking for/about .... For that matter, I would also like to know which *installed* pkgs are out of date. What is this 400.status-pkg you speak of ? TIA .... -- William A. Mahaffey III ---------------------------------------------------------------------- "The M1 Garand is without doubt the finest implement of war ever devised by man." -- Gen. George S. Patton Jr.