Hi
I run a daily portsnap from cron, using the following line:
/usr/sbin/portsnap cron update /dev/null 21 ;
/usr/local/sbin/portversion -vL=
Until recently, I only received a mail when there were ports to upgrade.
However, now I get this every day, even when there are no new ports
Tobias Roth wrote:
Hi
I run a daily portsnap from cron, using the following line:
/usr/sbin/portsnap cron update /dev/null 21 ;
/usr/local/sbin/portversion -vL=
Until recently, I only received a mail when there were ports to upgrade.
However, now I get this every day, even when
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
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
