You are unfortunately stuck between a rock and a hard place IMHO. While pkgng has this tool with # pkg check -adrs " -a Process all packages -B is used to reanalyse SHLIBS of installed packages. See pkg.conf(5) for more information on SHLIBS. -d is used to check for and install missing dependencies. -r is used to recompute sizes and checksums of installed packages. -s is used to find invalid checksums for installed packages."
Unfortunately there are no official repositories for pkgng built packages, so you have to keep building them yourself if you want to maintain an up-to-date system. And if a build breaks for a certain port you are stuck - you can't go and download an already built package for that one port that won't build. On the other hand, the old (legacy) package system had many problems, one of those problems being exactly this particular issue because the values for installed packages were not being kept in a database - so the capabilities of the legacy pkg system are limited. As a third option and if it is tolerable for you, you can wait until the official pkgng repos come on-line then make the switch to pkgng on your existing systems. Since your problem does appear to be urgent, you could just try re-installing the problem ports and all of its dependents. Regards. ----- 10-Current-amd64-using ccache-portstree merged with marcuscom.gnome3 & xorg.devel -- View this message in context: http://freebsd.1045724.n5.nabble.com/WANTED-Tool-to-verify-installed-package-port-consistancy-tp5810087p5810174.html Sent from the freebsd-ports mailing list archive at Nabble.com. _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
