Date: Fri, 29 Aug 2014 14:45:15 +0100 From: Arthur Chance <freebsd@qeng-ho.org> To: "William A. Mahaffey III" <wam@hiwaay.net>, "FreeBSD Questions !!!!" <freebsd-questions@freebsd.org> Subject: Re: Ports question .... Message-ID: <540083EB.5020801@qeng-ho.org> In-Reply-To: <5400793A.4090702@hiwaay.net> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?540083EB.5020801>