On Tue, 17 Jun 2003, Jeremy C. Reed wrote:

: > : On a related note, I believe it is more important or useful to have an
: > : option that forces some things to really DEPENDS. For example, if using
: > : texinfo, or openssl, or ncurses, or PAM, then it would be nice to have
: > : some option like FORCE_DEPENDS so when the package is used on another
: > : system, it will really need the prerequisites.
: >
: > Huh?  When does dependency registration *not* happen?
:
: Those examples above. For example, www/lynx: Build the package on a system
: with the needed libraries in the base system and then install it on a
: different system without those libraries.

"Sorry, not pkgsrc's fault."

If the needed libraries aren't on the destination system, what guarantee do
you have that pulling in a pkgsrc-compiled version (for your FORCE_DEPENDS
proposal) is in any way ABI compatible with the base-system version found on
the build box?

The base OS used for building a release must be *no newer* and have *no
additional base system libraries* than any machine on which you plan to
install a binary package.  This is common sense when building binaries of
any kind, not just from pkgsrc.

-- 
-- Todd Vierling <tv@pobox.com>