[pkgsrc/trunk]: pkgsrc Clear up a common misconception about buildlink3. The...

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

details:   https://anonhg.NetBSD.org/pkgsrc/rev/196c583b1513
branches:  trunk
changeset: 479167:196c583b1513
user:      jlam <jlam%pkgsrc.org@localhost>
date:      Fri Aug 06 15:27:21 2004 +0000

description:
Clear up a common misconception about buildlink3.  The reality is that
everything in /usr/include and /usr/lib (system header and library
paths) is always considered part of the package build environment;
buildlink3 only isolates package builds from everything outside of
those system paths.  As a consequence of this, LOCALBASE == "/usr"
effectively makes buildlink3 do nothing.

diffstat:

 Packages.txt |  6 ++++--
 1 files changed, 4 insertions(+), 2 deletions(-)

diffs (20 lines):

diff -r 66e8f253017e -r 196c583b1513 Packages.txt
--- a/Packages.txt      Fri Aug 06 15:09:35 2004 +0000
+++ b/Packages.txt      Fri Aug 06 15:27:21 2004 +0000
@@ -1,4 +1,4 @@
-# $NetBSD: Packages.txt,v 1.348 2004/08/05 20:55:11 jlam Exp $
+# $NetBSD: Packages.txt,v 1.349 2004/08/06 15:27:21 jlam Exp $
 ###########################################################################
 
                        ==========================
@@ -1783,7 +1783,9 @@
 
 This normalizes the environment in which a package is built so that the
 package may be built consistently despite what may other software may
-installed.
+installed.  Please note that the normal system header and library paths,
+e.g. /usr/include, /usr/lib, etc., are always searched -- buildlink3 is
+designed to insulate the package build from non-system-supplied software.
 
 
  8.1 Converting packages to use buildlink3