>Number:         17182
>Category:       pkg
>Synopsis:       Most pacakges are installed with restricted "uses Kerberos encryption code".
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    pkg-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Jun 06 07:56:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Takahiro Kambe
>Release:        NetBSD 1.6A
>Organization:
	
>Environment:
	
	
System: NetBSD edge.sky.yamashina.kyoto.jp 1.6A NetBSD 1.6A (FIVA20X) #144: Sat Jun 1 22:48:34 JST 2002 taca@edge.sky.yamashina.kyoto.jp:/usr/src/sys/arch/i386/compile/FIVA20X i386
Architecture: i386
Machine: i386
>Description:
	Most pacakges are installed with restricted "uses Kerberos
	encryption code".
>How-To-Repeat:
	Install some pkgsrc and check /var/db/pkg/${PKGNAME}/+BUILD_INFO.
	It will contain a line.  For example:

% egrep RESTRICTED /var/db/pkg/libtool-base-1.4.20010614nb9/+BUILD_INFO   
RESTRICTED= uses Kerberos encryption code

	I don't think that libtool is RESTRICTED by use of Kerberos
	encryption code.

>Fix:
	bsd.pkg.mk defines RESTRICTED when USE_KERBEROS is defined.

.if defined(USE_KERBEROS)
RESTRICTED?=		uses Kerberos encryption code
BUILD_DEFS+=		KERBEROS
.endif

	But bsd.pkg.mk includes "../../mk/bsd.prefs.mk" and it includes
	<bsd.own.mk>.  <bsd.own.mk> always define USE_KREBEROS by those
	lines:

# Set defaults for the USE_xxx variables.  They all default to "yes"
# unless the corresponding MKxxx variable is set to "no".
.for var in HESIOD KERBEROS SKEY YP
.if (${MK${var}} == "no")
USE_${var}:= no
.else
USE_${var}?= yes
.endif
.endfor

	It seems that USE_KERBEROS's meaning conflicts between base system
	and pkgsrc.  (I don't check existence of other conflicting MACRO.)

	This problem was pointed out by FUKAUMI Naoki <naoki@fukaumi.org>
	on netbsd@re.soum.co.jp (NetBSD mailing list in Japan).

>Release-Note:
>Audit-Trail:
>Unformatted: