In cases where some port definitely uses functions from a library
itself (rather than being pulled in via a dependency) I find it's
helpful to have that showing up, clearly it doesn't matter for
the tools/infrastructure but I bet I'm not the only one who greps
INDEX when trying to identify which ports are most important to
test following some library update, if something is only in
WANTLIB it won't show up there.

I don't want to see some huge list of unnecessary LIB_DEPENDS
(and I explicitly don't want a LIB_DEPENDS if a port *only* uses
something via a library dependency for example the chain of deps
pulled in by glib) and while I don't feel too strongly about it,
this diff feels to me like it's going a bit far in removing
things for the sake of it, I was actually going to write a mail
about it but wanted to write more than just "don't do this" so
Brad beat me to it ;)

My usual method would be to look through configure output or
builds docs for dependencies declared by upstream and list
them in LIB_DEPENDS when I'm writing the Makefile.

Reply via email to