> FWIW, portindexdb will generate INDEX-5.db just fine on 5-current. It
> doesn't have the problem with ruby bus erroring like portsdb -u does.
> Kent

This also works for me on 5.2.1-p9. Am I missing something in asking why 
couldn't "portsdb -u" be replaced by portindex? Obviously this couldn't 
happen now with the code-freeze for 5.3, but for 5.4?

[EMAIL PROTECTED] mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to