From owner-freebsd-questions@FreeBSD.ORG Fri Aug 29 13:45: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 33245221 for ; Fri, 29 Aug 2014 13:45:18 +0000 (UTC) Received: from blue.qeng-ho.org (blue.qeng-ho.org [217.155.128.241]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BCDB71EC5 for ; Fri, 29 Aug 2014 13:45:17 +0000 (UTC) Received: from fileserver.home.qeng-ho.org (localhost [127.0.0.1]) by fileserver.home.qeng-ho.org (8.14.7/8.14.5) with ESMTP id s7TDjF7X071207; Fri, 29 Aug 2014 14:45:15 +0100 (BST) (envelope-from freebsd@qeng-ho.org) Message-ID: <540083EB.5020801@qeng-ho.org> Date: Fri, 29 Aug 2014 14:45:15 +0100 From: Arthur Chance User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: "William A. Mahaffey III" , "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> In-Reply-To: <5400793A.4090702@hiwaay.net> 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 13:45:18 -0000 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.