diff options
| author | grant <grant> | 2004-05-08 23:46:20 +0000 |
|---|---|---|
| committer | grant <grant> | 2004-05-08 23:46:20 +0000 |
| commit | b19847276671880f438f17bba0881256dff656cc (patch) | |
| tree | 6034da7d2148a1d215f2894d90d608229d7fea32 /mk | |
| parent | bc9bf24eb94ab4b6699276c75160a18f733eee03 (diff) | |
| download | pkgsrc-b19847276671880f438f17bba0881256dff656cc.tar.gz | |
remove a word which shouldn't be there.
Diffstat (limited to 'mk')
| -rw-r--r-- | mk/buildlink3/BUILDLINK3_DG | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/mk/buildlink3/BUILDLINK3_DG b/mk/buildlink3/BUILDLINK3_DG index 8203f4e8cac..473adfefe83 100644 --- a/mk/buildlink3/BUILDLINK3_DG +++ b/mk/buildlink3/BUILDLINK3_DG @@ -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 @@ into native toolchain equivalents. 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 @@ The following real-life example buildlink3.mk is taken from 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}+ |