[pkgsrc/trunk]: pkgsrc Note why USE_BUILTIN.<pkg> may be "yes" even if IS_BUI...

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

details:   https://anonhg.NetBSD.org/pkgsrc/rev/4ed5dfa87795
branches:  trunk
changeset: 479325:4ed5dfa87795
user:      jlam <jlam%pkgsrc.org@localhost>
date:      Thu Aug 12 10:07:28 2004 +0000

description:
Note why USE_BUILTIN.<pkg> may be "yes" even if IS_BUILTIN.<pkg> is "no".

diffstat:

 Packages.txt |  9 ++++++---
 1 files changed, 6 insertions(+), 3 deletions(-)

diffs (30 lines):

diff -r cf8cb84b60f6 -r 4ed5dfa87795 Packages.txt
--- a/Packages.txt      Thu Aug 12 09:26:05 2004 +0000
+++ b/Packages.txt      Thu Aug 12 10:07:28 2004 +0000
@@ -1,4 +1,4 @@
-# $NetBSD: Packages.txt,v 1.350 2004/08/07 10:15:47 wiz Exp $
+# $NetBSD: Packages.txt,v 1.351 2004/08/12 10:07:28 jlam Exp $
 ###########################################################################
 
                        ==========================
@@ -2061,7 +2061,7 @@
 
 The first section sets IS_BUILTIN.<pkg> depending on if <pkg> really exists
 in the base system.  This should not be a base system software with similar
-functionality to <pkg>; it should only be "yes" if the actual package
+functionality to <pkg>; it should only be "yes" if the actual package is
 included as part of the base system.  This variable is only used internally
 within the builtin.mk file.
 
@@ -2075,7 +2075,10 @@
 listed in BUILDLINK_DEPENDS.<pkg>.  This is typically done by comparing
 BUILTIN_PKG.<pkg> against each of the dependencies in
 BUILDLINK_DEPENDS.<pkg>.  USE_BUILTIN.<pkg> _must_ be set to the correct
-value by the end of the builtin.mk file.
+value by the end of the builtin.mk file.  Note that USE_BUILTIN.<pkg> may
+be "yes" even if IS_BUILTIN.<pkg> is "no" because we may make the
+determination that the built-in version of the software is similar enough
+to be used as a replacement.
 
 The last section is guarded by CHECK_BUILTIN.<pkg>, and includes code that
 uses the value of USE_BUILTIN.<pkg> set in the previous section.  This