svn commit: r364287 - head/ports-mgmt/pkg-devel

[Tijl Coosemans]

On Mon, 11 Aug 2014 11:51:49 -0400 Adam Weinberger wrote:
> Can one of the build cluster machines start logging the actual shlib
> links of each port, after the package is built? That would make it so
> deliciously easy, if a porter could just ask the system for a
> comprehensive list of every port that contains links to a specific
> library.

There's no dedicated query for this that I know of, but you can get a
list like this:

% pkg rquery '%o %B' | grep 'libpaper\.so'
print/a2ps libpaper.so.1
print/c2ps libpaper.so.1
print/cups-base libpaper.so.1
print/ghostscript8 libpaper.so.1
print/ghostscript8-nox11 libpaper.so.1
print/ghostscript9 libpaper.so.1
print/ghostscript9-agpl libpaper.so.1
print/ghostscript9-agpl-nox11 libpaper.so.1
print/ghostscript9-nox11 libpaper.so.1
graphics/jpeg2ps libpaper.so.1
print/lprps libpaper.so.1
print/psutils libpaper.so.1
editors/ted libpaper.so.1
print/tex-dvipdfmx libpaper.so.1
print/tex-dvipsk libpaper.so.1
print/tex-xdvik libpaper.so.1
games/tuxpaint libpaper.so.1
games/tuxpaint-config libpaper.so.1

This only captures default options of course.