From 34d11d8a0f59e1c62bc5b1cc1046d3275e061062 Mon Sep 17 00:00:00 2001 From: jlam Date: Sat, 23 Jun 2001 19:26:48 +0000 Subject: Generalize how the dependency pattern may be specified. Instead of just FOO_REQD=1.0 being converted to foo>=1.0, one can now directly specify the dependency pattern as FOO_DEPENDS=foo>=1.0. This allows things like JPEG_DEPENDS=jpeg-6b, or fancier expressions like for postgresql-lib. Change existing FOO_REQD definitions in Makefiles to FOO_DEPENDS. --- security/PAM/buildlink.mk | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) (limited to 'security/PAM') diff --git a/security/PAM/buildlink.mk b/security/PAM/buildlink.mk index e6617e50543..a59b8503c54 100644 --- a/security/PAM/buildlink.mk +++ b/security/PAM/buildlink.mk @@ -1,10 +1,11 @@ -# $NetBSD: buildlink.mk,v 1.6 2001/06/11 01:59:38 jlam Exp $ +# $NetBSD: buildlink.mk,v 1.7 2001/06/23 19:26:59 jlam Exp $ # # This Makefile fragment is included by packages that use libpam. # # To use this Makefile fragment, simply: # -# (1) Optionally define PAM_REQD to the version of pam desired. +# (1) Optionally define BUILDLINK_DEPENDS.pam to the dependency pattern +# for the version of pam desired. # (2) Include this Makefile fragment in the package Makefile, # (3) Add ${BUILDLINK_DIR}/include to the front of the C preprocessor's header # search path, and @@ -14,8 +15,8 @@ .if !defined(PAM_BUILDLINK_MK) PAM_BUILDLINK_MK= # defined -PAM_REQD?= 0.72 -DEPENDS+= PAM>=${PAM_REQD}:../../security/PAM +BUILDLINK_DEPENDS.pam?= PAM>=0.72 +DEPENDS+= ${BUILDLINK_DEPENDS.pam}:../../security/PAM BUILDLINK_PREFIX.pam= ${LOCALBASE} BUILDLINK_FILES.pam= include/security/* -- cgit v1.2.3