On Wed, 6 Sep 2000, Hubert Feyrer wrote:

> OK, and what do you suggest then? Tell them that a lib of <newer version>
> would be required, judging from information encoded in the (new) "app"
> pkg? 

Yes, and also update the DEPENDS in the app pkgsrc (if it isn't fixed
already), and delete the app binary package with the broken dependency
from the server. [We shouldn't say "app" depends on lib>=1.1 unless
"app" built against lib-1.2 is known to work with lib-1.1. I don't
want to lay a heavy "burden of proof" on the pkgsrc maintainer though,
I just want a way to fix it when someone reports a problem.]

> And if so, assuming that the information which depends _exactly_ a
> pkg was compiled against is only used for user information, how do the
> users get this information? Printed automatically? When?

"tar xf pkg-x.tgz '+BUILD_DEPENDS'" is good enough for me. The
information is for the maintainers of the binary package collection,
not for the user.