diff options
| author | reed <reed> | 2005-09-14 15:55:35 +0000 |
|---|---|---|
| committer | reed <reed> | 2005-09-14 15:55:35 +0000 |
| commit | ab896c2c7816ad3fd42bcdb45da83304748da6f7 (patch) | |
| tree | ce577768e25db7c1963854bef53ba4996c2fd520 /doc/guide | |
| parent | bfe0856eee41c489597dd44bb89623c619799cfc (diff) | |
| download | pkgsrc-ab896c2c7816ad3fd42bcdb45da83304748da6f7.tar.gz | |
In the "converting packages to use buildlink" section,
mention setting BUILDLINK_DEPENDS.foo.
(Suggested by Steven M. Bellovin on tech-pkg.)
Diffstat (limited to 'doc/guide')
| -rw-r--r-- | doc/guide/files/buildlink.xml | 10 |
1 files changed, 9 insertions, 1 deletions
diff --git a/doc/guide/files/buildlink.xml b/doc/guide/files/buildlink.xml index 1aa3d93705b..617a4832b37 100644 --- a/doc/guide/files/buildlink.xml +++ b/doc/guide/files/buildlink.xml @@ -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> |