[pkgsrc/trunk]: pkgsrc/doc/guide/files In the "converting packages to use bui...

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

details:   https://anonhg.NetBSD.org/pkgsrc/rev/4f4d141560cc
branches:  trunk
changeset: 499213:4f4d141560cc
user:      reed <reed%pkgsrc.org@localhost>
date:      Wed Sep 14 15:55:35 2005 +0000

description:
In the "converting packages to use buildlink" section,
mention setting BUILDLINK_DEPENDS.foo.
(Suggested by Steven M. Bellovin on tech-pkg.)

diffstat:

 doc/guide/files/buildlink.xml |  10 +++++++++-
 1 files changed, 9 insertions(+), 1 deletions(-)

diffs (24 lines):

diff -r 782b2667d1c1 -r 4f4d141560cc doc/guide/files/buildlink.xml
--- a/doc/guide/files/buildlink.xml     Wed Sep 14 14:33:01 2005 +0000
+++ b/doc/guide/files/buildlink.xml     Wed Sep 14 15:55:35 2005 +0000
@@ -1,4 +1,4 @@
-<!-- $NetBSD: buildlink.xml,v 1.7 2005/09/02 19:12:37 rillig Exp $ -->
+<!-- $NetBSD: buildlink.xml,v 1.8 2005/09/14 15:55:35 reed Exp $ -->
 
 <chapter id="buildlink">
   <title>Buildlink methodology</title>
@@ -75,6 +75,14 @@
 
     <programlisting>.include "../../category/foo/buildlink3.mk"</programlisting>
 
+    <para>The buildlink3.mk files usually define the required dependencies.
+    If you need a newer version of the dependency when using buildlink3.mk
+    files, then you can define it in your Makefile; for example:
+    </para>
+
+    <programlisting>BUILDLINK_DEPENDS.foo+=   foo>=1.1.0
+    .include "../../category/foo/buildlink3.mk"</programlisting>
+
     <para>There are several <filename>buildlink3.mk</filename>
       files in <filename>pkgsrc/mk</filename>
       that handle special package issues:</para>