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.
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.
email@example.com mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"