Commit graph

5 commits

Author SHA1 Message Date
salo
b26c32d51a Use tabs, not spaces. 2005-06-16 17:40:56 +00:00
tv
c36fe675e2 Add OS conditional blocks to exclude some PAM implementations from
selection, thus allowing "none" to be a correct result on systems where
PAM is currently unavailable.
2005-04-25 14:21:47 +00:00
jlam
bff1eecc97 Modify linux-pam and solaris-pam builtin.mk files to be more general
in their tests for built-in versions of the PAM implementations.  The
MacOS X case now collapses nicely into the linux-pam case.  Allow
pam.buildlink3.mk to use solaris-pam as an accepted PAM implementation.
2005-01-14 07:54:20 +00:00
jlam
643b26af82 We need to check that IS_BUILTIN.<pam> is "yes", not just that it's empty. 2005-01-14 07:37:39 +00:00
jlam
1b5734f517 Create a pam.buildlink3.mk file that is used by PAM-using packages.
It includes the correct buildlink3.mk file from either Linux-PAM
(security/PAM) or OpenPAM (security/openpam) and eventually will
support solaris-pam.  pam.buildlink3.mk will:

	* set PAMBASE to the base directory of the PAM files;
	* set PAM_TYPE to the PAM implementation used.

There are two variables that can be used to tweak the selection of
the PAM implementation:

PAM_DEFAULT is a user-settable variable whose value is the default
	PAM implementation to use.

PAM_ACCEPTED is a package-settable list of PAM implementations
	that may be used by the package.

Modify most packages that include PAM/buildlink3.mk to include
pam.buildlink3.mk instead.
2005-01-14 05:15:39 +00:00