Date: Sun, 29 Jul 2007 15:34:21 +0400 (GST) From: Rakhesh Sasidharan <rakhesh@rakhesh.com> To: "Garrett Cooper" <youshi10@u.washington.edu>, freebsd-questions@freebsd.org Subject: Re: portsnap from cron Message-ID: <52486.212.72.24.148.1185708861.squirrel@rakhesh.com> In-Reply-To: <46AC59C3.7080804@fsck.ch> References: <46AC527F.4010305@fsck.ch> <46AC58B0.6060808@u.washington.edu> <46AC59C3.7080804@fsck.ch>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, July 29, 2007 13:11, Tobias Roth wrote: > Garrett Cooper wrote: > >> That's not going to change until portversion changes. The problem is >> most likely that portsnap touches the file and portversion finds it >> necessary to update the portsdb. Processing the text from portversion >> will yield the info you want. >> Cheers, >> -Garrett > > Ohh, now at least I have an idea why it is suddenly happening, and how > to fix it. I'll either run portsdb between portsnap and portversion, or > try to grep out the unneeded stuff. > I use pkg_version. Same functionality as portversion, but its slower coz it doesn't use the INDEX.db file. Maybe you could use that to avoid the messages? :) (The speed won't matter coz its run as a cron job anyways!) Do 'pkg_version -l "<" ' to get a list of ports that need updating ..... Thanks, Rakhesh
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?52486.212.72.24.148.1185708861.squirrel>