On Sun, Sep 15, 2013 at 10:42:51AM -0400, Richard Thornton wrote: > > So am I safe to ^C this process and try again? I don't want to corrupt > > the package database since I'll probably not be able to fix it.
The package database is *very* resilient. First, the pkgtools operate in such a way as to make sure everything is consistent most of the time. Second, they know about ^C, and will abort operations in a smart way. Finally, there's a pkg_check tool that's occasionally useful, most often after a power outage in the middle of a package update... pkg_add does what it can, but it can't do a lot against unfinished writes leading to fsck. Also, if a machine ever crashes in the middle of an installation, pkg_add is smart enough to recognize that files have been already installed from an existing package. e.g., perform a pkg_add foo rm -rf /var/db/pkg/foo-* pkg_add foo -> will say something like "files detected that match a foo package that wasn't registered. Repair ? (Y/n/a)"
