pkgsrc/security/PAM/module.mk, branch pkgsrc_2008Q2

Don't check for USE_BUILDLINK3 anymore in these files. These are included

2005-03-24T22:42:58Z

by other package Makefiles, and with the deprecation of USE_BUILDLINK3 support in the infrastructure files, these had the potential to break existing packages.

Create a pam.buildlink3.mk file that is used by PAM-using packages.

2005-01-14T05:15:39Z

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.

* Rename the buildlink module name associated with the security/PAM

2005-01-14T00:08:46Z

package from "pam" to "linux-pam". * Rewrite PAM/builtin.mk to check that we have Linux-PAM, and re-classify MacOS X's PAM as Linux-PAM because it _is_, according to to Apple. Also don't use BUILDLINK_TRANSFORM.* to rewrite header file paths -- just use a symlink so that can be used to find .

Remove support for buildlink2.

2004-05-11T04:39:03Z

First cut at a common module.mk file to be included by PAM module packages.

2004-01-08T00:08:23Z