[pkgsrc/trunk]: pkgsrc/mail/imap-uw If OPSYS is NetBSD and there is no PAM he...

[dholland <dholland%pkgsrc.org@localhost>]

details:   https://anonhg.NetBSD.org/pkgsrc/rev/a50cd99d4372
branches:  trunk
changeset: 601375:a50cd99d4372
user:      dholland <dholland%pkgsrc.org@localhost>
date:      Tue Mar 20 16:34:32 2012 +0000

description:
If OPSYS is NetBSD and there is no PAM header in /usr/include, include
pam.buildlink3.mk. This is wrong and a hack, but it gets the package
building again in my test environment. Someone please revert this and
do it right.

Currently there seems to be logic for enabling PAM in the build or not
on various platforms depending on whether native PAM appears to exist.
This is higly bogus; the package should be cleaned up so it either
depends on PAM or doesn't, regardless of platform, or preferably makes
it a build option.

XXX.

diffstat:

 mail/imap-uw/Makefile |  8 +++++++-
 1 files changed, 7 insertions(+), 1 deletions(-)

diffs (22 lines):

diff -r c0b42fa094a5 -r a50cd99d4372 mail/imap-uw/Makefile
--- a/mail/imap-uw/Makefile     Tue Mar 20 16:27:40 2012 +0000
+++ b/mail/imap-uw/Makefile     Tue Mar 20 16:34:32 2012 +0000
@@ -1,4 +1,4 @@
-# $NetBSD: Makefile,v 1.134 2011/01/30 01:33:44 markd Exp $
+# $NetBSD: Makefile,v 1.135 2012/03/20 16:34:32 dholland Exp $
 #
 # ATTENTION:
 # The Kerberos support in this software is known to be problematic. If you
@@ -69,6 +69,12 @@
 BUILD_TARGET.*=                neb
 MESSAGE_SRC=           ${PKGDIR}/MESSAGE
 
+# XXX this is not the right approach - should either depend on pam or
+# not, or make it an option.
+.if ${OPSYS} == NetBSD && !exists(/usr/include/security/pam_appl.h)
+.include "../../mk/pam.buildlink3.mk"
+.endif
+
 .include "options.mk"
 
 # The defaults for these values are set in pkgsrc/mk/defaults/mk.conf.