docs/50349: make release fails with NO_OPENSSH and ! NOKERBEROS
stijn at win.tue.nl
Mon Oct 6 10:20:11 UTC 2003
On Sun, Oct 05, 2003 at 09:46:29PM +0300, Ruslan Ermilov wrote:
> On Sun, Oct 05, 2003 at 12:14:32AM -0400, Ken Smith wrote:
> > On Sat, Oct 04, 2003 at 08:30:12PM +0100, Mark Murray wrote:
> > > The crypto stuff in nicely separated out, and I wouldn't mind seeing
> > > further separation (dev tools, LPR, sendmail, etc) done as separately
> > > installable components, similar to the crypto install.
> > A current interest is having some sort of binary updates system
> > in place. Everyone I talk to about the various issues, projects in
> > motion, etc. say this further separation of stuff would help that
> > effort a LOT.
> The (crypto) stuff is already well separated, it's just that
> we don't want to further complicate release/Makefile to
> account for the NOCRYPT option -- it's much easier to remove
> the unneeded bits after release is rolled.
What about this then:
[stijn at pcwin002] <~> ldd /usr/bin/fetch
libfetch.so.3 => /usr/lib/libfetch.so.3 (0x28076000)
libssl.so.3 => /usr/lib/libssl.so.3 (0x28083000)
libcrypto.so.3 => /lib/libcrypto.so.3 (0x280b5000)
libc.so.5 => /lib/libc.so.5 (0x281c3000)
It seems to me that a release build with crypto and installed without
will miss /usr/bin/fetch, or will it simply not work? Haven't tried yet,
but I was just wondering.
"Diane, 2:15 in the afternoon, November 14. Entering town of Twin Peaks.
Five miles south of the Canadian border, twelve miles west of the state
line. Never seen so many trees in my life. As W.C. Fields would say, I'd
rather be here than Philadelphia."
-- Special Agent Dale Cooper, "Twin Peaks"
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 187 bytes
Desc: not available
More information about the freebsd-doc