summaryrefslogtreecommitdiff
path: root/Packages.txt
diff options
context:
space:
mode:
authorjlam <jlam>2001-08-22 17:53:30 +0000
committerjlam <jlam>2001-08-22 17:53:30 +0000
commit060893d4e7782bd7ef6e0cb22b1b770195d4aa6c (patch)
treee88656ecd8d24847ad425fe6ecca1564f9550bc5 /Packages.txt
parent32204583600eb49b0fbcc06c1838aef0d8d4be7d (diff)
downloadpkgsrc-060893d4e7782bd7ef6e0cb22b1b770195d4aa6c.tar.gz
Define the terms "weakly-buildlinked" and "strongly-buildlinked"
(my math background shows...).
Diffstat (limited to 'Packages.txt')
-rw-r--r--Packages.txt4
1 files changed, 3 insertions, 1 deletions
diff --git a/Packages.txt b/Packages.txt
index 7e8f214e3a2..f75961f340c 100644
--- a/Packages.txt
+++ b/Packages.txt
@@ -1,4 +1,4 @@
-# $NetBSD: Packages.txt,v 1.177 2001/08/13 18:09:06 hubertf Exp $
+# $NetBSD: Packages.txt,v 1.178 2001/08/22 17:53:30 jlam Exp $
###########################################################################
==========================
@@ -1498,9 +1498,11 @@ these files is two-fold:
(1) Cause all headers and libraries used by a particular package to be
found in a known location during the configure and build process.
+ These packages are said to be "weakly-buildlinked".
(2) Cause _only_ those headers and libraries used by a particular package
to be found during the configure and build process.
+ These packages are said to be "strongly-buildlinked".
8.1 Using buildlink.mk files