'make package' packing wrong binaries?

["John D. Baker" <jdbaker%consolidated.net@localhost>]

This is a strange issue that I've been dealing with for at least a couple
of cycles.  Naturally, critical libraries like libcrypto.so* and libssl.so*
leave the old versions in place when the system is updated with a newer
version.  I am updating from 10.1_STABLE to 11.0_RC2 (and previously, _BETA)
on both amd64 and i386.

When packages are rebuilt, however, I've been having the problem that the
binary installed in 'make replace' uses the newer version of the library,
but the binary that was packaged uses the old version of the library.  Thus,
when I go to install/update that package on a system which never had the
old version of the library, the installation (or worse, the update) fails.

The most common offender is "security/sudo".  The binary installed on the
build host in 'make replace' uses "/usr/lib/libcrypto.so.16", but the binary
that was packaged uses "/usr/lib/libcrypto.so.15".  Then when I use that
package to update another machine which only has "libcrypto.so.16", the
old version of sudo is removed and the update fails and I'm left without
'sudo'.

More recently, "ups-nut" has done the same thing, but with "libssl.so*".
The binaries installed on the build host during 'make replace' use the
current "libssl.so.16", but the binaries that were packaged use
"libssl.so.15".

Going back and running 'make package' again packages binaries using the
correct libraries.  So it looks like the package-creation stage of at
least "sudo" and "ups-nut" are packaging the binaries that are installed
(before "replace" happens) instead of the binaries that were installed to
".destdir".

-- 
|/"\ John D. Baker, KN5UKS               NetBSD     Darwin/MacOS X
|\ / jdbaker[snail]consolidated[flyspeck]net  OpenBSD            FreeBSD
| X  No HTML/proprietary data in email.   BSD just sits there and works!
|/ \ GPGkeyID:  D703 4A7E 479F 63F8 D3F4  BD99 9572 8F23 E4AD 1645