[pkgsrc/trunk]: pkgsrc/mk/buildlink3 remove a word which shouldn't be there.

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

details:   https://anonhg.NetBSD.org/pkgsrc/rev/2a4117acb147
branches:  trunk
changeset: 475015:2a4117acb147
user:      grant <grant%pkgsrc.org@localhost>
date:      Sat May 08 23:46:20 2004 +0000

description:
remove a word which shouldn't be there.

diffstat:

 mk/buildlink3/BUILDLINK3_DG |  6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)

diffs (27 lines):

diff -r d00908c2224b -r 2a4117acb147 mk/buildlink3/BUILDLINK3_DG
--- a/mk/buildlink3/BUILDLINK3_DG       Sat May 08 22:21:06 2004 +0000
+++ b/mk/buildlink3/BUILDLINK3_DG       Sat May 08 23:46:20 2004 +0000
@@ -1,4 +1,4 @@
-$NetBSD: BUILDLINK3_DG,v 1.3 2004/02/05 08:50:38 jlam Exp $
+$NetBSD: BUILDLINK3_DG,v 1.4 2004/05/08 23:46:20 grant Exp $
 
  0 Developer's guide to buildlink3
  =================================
@@ -44,7 +44,7 @@
 
 buildlink3.mk files have two major differences over buildlink2.mk
 files.  The first, most noticeable difference is that buildlink3.mk
-generally don't have contain a BUILDLINK_FILES definition.  This is
+generally don't contain a BUILDLINK_FILES definition.  This is
 because buildlink3 automatically determines which files to symlink
 into ${BUILDLINK_DIR} by examining the PLIST of the installed package.
 The second difference is that buildlink3.mk files keep track of how
@@ -92,7 +92,7 @@
 graphics/tiff:
 
 ------------8<------------8<------------8<------------8<------------
-# $NetBSD: BUILDLINK3_DG,v 1.3 2004/02/05 08:50:38 jlam Exp $
+# $NetBSD: BUILDLINK3_DG,v 1.4 2004/05/08 23:46:20 grant Exp $
 
 BUILDLINK_DEPTH:=      ${BUILDLINK_DEPTH}+
 TIFF_BUILDLINK3_MK:=   ${TIFF_BUILDLINK3_MK}+