On Fri, 21 Nov 2003, Jeremy C. Reed wrote:

> The list of files generated by Thomas K.'s getalldepends.sh script is very
> long!

It has over 600 packages that require tiff.

I have a feeling that tiff isn't really used by that many.

It would be interesting to do an automated build of these 600 packages
that moved the /usr/pkg/lib/libtiff.* out of the way for each one to see
if it breaks the build. What do you think? Any ideas?

Or is there an easy way to see what binaries are built using a static .a
library (like libtiff.a)?

And with the PKG_DEVELOPER, you can check in +BUILD_INFO for use of
"REQUIRES=" of tiff.so.

It doesn't seem right to bump 600 packages' versions with PKGREVISION if
they don't really use any tiff. What do other package projects do?

   Jeremy C. Reed
   http://bsd.reedmedia.net/