summaryrefslogtreecommitdiff
path: root/Packages.txt
diff options
context:
space:
mode:
authorhubertf <hubertf@pkgsrc.org>1998-03-05 16:37:14 +0000
committerhubertf <hubertf@pkgsrc.org>1998-03-05 16:37:14 +0000
commit126cb5e5c3500567ea890419fde3aa23a6fcf734 (patch)
tree79d6fc28a0d9d9884452a6b54423b6f53645719a /Packages.txt
parent3cb14bf074071cf73daa0b38e391dea102305a1a (diff)
downloadpkgsrc-126cb5e5c3500567ea890419fde3aa23a6fcf734.tar.gz
Add note on use of mk.conf variables.
Diffstat (limited to 'Packages.txt')
-rw-r--r--Packages.txt19
1 files changed, 18 insertions, 1 deletions
diff --git a/Packages.txt b/Packages.txt
index 4fa66db50f8..29b38c0bc14 100644
--- a/Packages.txt
+++ b/Packages.txt
@@ -1,4 +1,4 @@
-# $NetBSD: Packages.txt,v 1.20 1998/03/05 15:26:03 tron Exp $
+# $NetBSD: Packages.txt,v 1.21 1998/03/05 16:37:14 hubertf Exp $
###########################################################################
==========================
@@ -924,6 +924,23 @@ MANCOMPRESSED= 1
.endif
+ 9.10 How to pull in variables from /etc/mk.conf
+ ===============================================
+
+The problem with package-defined variables that can be overridden via
+/etc/mk.conf is that the values of these variables aren't known at the
+beginning of the Makefile, and thus can't be used in .if statements. It's
+OK to use them like any other variable in expansions ("${VAR}"), but not in
+.if-statements, though.
+
+Here's the preferred way to handle things if you want to include variables
+in .if statements:
+
+1. in the pkg Makefile, set all the pre-install etc targets.
+2. in the pkg Makefile, .include <bsd.port.mk>
+3. Then put all the .if defined(USE_SOCKS), .if defined(USE_IDEA) etc
+
+
10 Submitting
=============