summaryrefslogtreecommitdiff
path: root/mk/pam.buildlink3.mk
AgeCommit message (Collapse)AuthorFilesLines
2005-06-16Use tabs, not spaces.salo1-2/+2
2005-04-25Add OS conditional blocks to exclude some PAM implementations fromtv1-2/+14
selection, thus allowing "none" to be a correct result on systems where PAM is currently unavailable.
2005-01-14Modify linux-pam and solaris-pam builtin.mk files to be more generaljlam1-2/+2
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-14We need to check that IS_BUILTIN.<pam> is "yes", not just that it's empty.jlam1-2/+3
2005-01-14Create a pam.buildlink3.mk file that is used by PAM-using packages.jlam1-0/+76
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.