Commit graph

20 commits

Author SHA1 Message Date
wiz
8c8f18c61c Let the rc.d script start kdc detached, as is the default for
the in-tree kdc.
From Jukka Salmi in PR 24489, ok'd by lukem@.
Bump PKGREVISION to 1.
2004-02-23 12:35:11 +00:00
markd
59215063a5 configure looks for and finds -ltermcap too late in the process for it to
be linked in when testing -lreadline usability so that test fails on
Solaris - so pass that lib into configure at the start via the environment.

Also allow optional use of db4 rather that db.
2004-02-22 11:59:50 +00:00
jlam
bf6e059da4 Reorder some lines so that BUILDLINK_USE_BUILTIN.<pkg> set in the
environment overrides all other settings.
2004-02-18 16:35:27 +00:00
jlam
3ebe053d90 LIBTOOL_OVERRIDE and SHLIBTOOL_OVERRIDE are now lists of shell globs
relative to ${WRKSRC}.  Remove redundant LIBTOOL_OVERRIDE settings that
are automatically handled by the default setting in bsd.pkg.mk.
2004-02-14 17:21:49 +00:00
jlam
d2b62c66fb Create a new variable PREFER_NATIVE that has the opposite semantics
as PREFER_PKGSRC.  Preferences are determined by the most specific
instance of the package in either PREFER_PKGSRC or PREFER_NATIVE.  If
a package is specified in neither or in both variables, then PREFER_PKGSRC
has precedence over PREFER_NATIVE.
2004-02-12 02:35:06 +00:00
jlam
1edfa505ed Reorganize code so that any dependencies are checked as part of deciding
whether the software is built-in or not.  This facilitates implementing
the forthcoming PKGSRC_NATIVE variable.
2004-02-12 01:59:37 +00:00
jlam
7699290f10 If we're passing through MAKEFLAGS variables whose values may contain
spaces, use the :Q modifier instead of double-quoting the value.  This
avoids breakage when executing the just-in-time su targets.
2004-02-06 19:04:24 +00:00
jlam
317cc72791 Make PREFER_PKGSRC just yes/no or a list of packages. This makes it
simpler to understand.
2004-02-05 07:17:14 +00:00
jlam
e7133cac25 Rename BUILDLINK_PREFER_PKGSRC to PREFER_PKGSRC so that we can use its
value outside of buildlink-related files.
2004-02-05 07:06:15 +00:00
jlam
07a9d8dfb2 Support a new global variable:
BUILDLINK_PREFER_PKGSRC
	This variable determines whether or not to prefer the pkgsrc
	versions of software that is also present in the base system.

	This variable is multi-state:
		defined, or "yes"	always prefer the pkgsrc versions
		not defined, or "no"	only use the pkgsrc versions if
					needed by dependency requirements

	This can also take a list of packages for which to prefer the
	pkgsrc-installed software.  The package names may be found by
	consulting the value added to BUILDLINK_PACKAGES in the
	buildlink[23].mk files for that package.
2004-02-05 06:58:02 +00:00
jlam
3d74ada992 Pretend that all versions of NetBSD newer than 1.6U have Heimdal-0.6. 2004-02-02 11:30:45 +00:00
jlam
01a5abff01 Support BUILDLINK_DEPENDS.<pkg> being a list of values. 2004-01-24 03:12:31 +00:00
jlam
83532f92f6 Support a new yes/no variable "KERBEROS_PREFIX_CMDS" that can be used by
Kerberos implementation packages to decide whether to prefix certain
commands with a "k" to differentiate it from system tools with similar
names.  KERBEROS_PREFIX_CMDS defaults to "no".
2004-01-15 12:48:00 +00:00
markd
f8c2eb7eb1 Fix build with gcc3. 2004-01-13 02:05:29 +00:00
jlam
18ec955c8a whitespace. 2004-01-13 00:00:32 +00:00
jlam
a41e499e44 Note CONFLICT with forthcoming mit-krb5 package. 2004-01-11 00:00:28 +00:00
jlam
99ac5d408b Add a rc.d script to start the kdc daemon on the Kerberos master server. 2004-01-10 21:59:29 +00:00
jlam
c0a16733a6 Back out previous. This doesn't work as expected and needs more thought. 2004-01-10 21:35:26 +00:00
jlam
ca86c17d51 The buildlink3 wrappers automatically remove -I/usr/include/* from the
command line options.  We need -I/usr/include/krb5 to build against
heimdal, so symlink the headers in /usr/include/krb5 into ${BUILDLINK_DIR}
so they can be found.
2004-01-10 19:44:16 +00:00
jlam
694ff19aff Initial import of heimdal-0.6 into security/heimdal.
Heimdal is a free implementation of Kerberos 5.

Kerberos is a system for authenticating users and services on a network.
It is built upon the assumption that the network is "unsafe".  Kerberos
is a trusted third-party service.  That means that there is a third
party (the Kerberos server) that is trusted by all the entities on the
network (users and services, usually called "principals").  All
principals share a secret password (or key) with the Kerberos server and
this enables principals to verify that the messages from the Kerberos
server are authentic.  Thus trusting the Kerberos server, users and
services can authenticate each other.
2004-01-10 14:56:44 +00:00