Date: Sat, 17 Jan 2004 11:22:37 -0800 (PST) From: Ruslan Ermilov <ru@FreeBSD.org> To: src-committers@FreeBSD.org, cvs-src@FreeBSD.org, cvs-all@FreeBSD.org Subject: cvs commit: src/secure Makefile src/release Makefile Message-ID: <200401171922.i0HJMb8q082325@repoman.freebsd.org>
next in thread | raw e-mail | index | archive | help
ru 2004/01/17 11:22:37 PST
FreeBSD src repository
Modified files:
secure Makefile
release Makefile
Log:
Once upon a time we had both "crypto" and "krb5" distributions,
and rebuilt some bits with crypto but without Kerberos support
(most notably SSH) during "make release", to put them into the
"crypto" distribution.
Now that we don't ship the separate "krb5" distribution anymore
(it's now part of the "crypto" distribuion), don't waste time
recompiling SSH bits without crypto and without Kerberos support
in an attempt to put them in the "base" distribution -- it just
doesn't work as SSH always uses crypto code.
We avoid this by not rebuilding KPROGS from kerberos5/Makefile in
release/Makefile and adding "libpam" to SPROGS in secure/Makefile
to ensure it's still rebuilt without crypto support for the "base"
distribution. (Disabling crypto (NOCRYPT) also disables building
of Kerberos-related PAM modules, and it's OK to depend on this.)
This should be a no-op change saving some "make release" time.
Revision Changes Path
1.831 +1 -2 src/release/Makefile
1.23 +1 -0 src/secure/Makefile
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200401171922.i0HJMb8q082325>