summaryrefslogtreecommitdiff
path: root/doc/guide
diff options
context:
space:
mode:
authorreed <reed>2005-09-14 16:46:13 +0000
committerreed <reed>2005-09-14 16:46:13 +0000
commit4795d7de68053cb8348934d239a2c31bda44addf (patch)
tree1396c80ccc87e1fc12c0beb412bf3efc1d27a1bd /doc/guide
parent215aa3ede811e952b6d18886d4053854c4444982 (diff)
downloadpkgsrc-4795d7de68053cb8348934d239a2c31bda44addf.tar.gz
Mention USE_TOOLS also may express a dependency.
Todo: USE_TOOLS should be documented, such as :pkgsrc, :run, :build (I started working on a files/tools.xml.)
Diffstat (limited to 'doc/guide')
-rw-r--r--doc/guide/files/fixes.xml7
1 files changed, 4 insertions, 3 deletions
diff --git a/doc/guide/files/fixes.xml b/doc/guide/files/fixes.xml
index c23ca6868f7..8c47b1e05ba 100644
--- a/doc/guide/files/fixes.xml
+++ b/doc/guide/files/fixes.xml
@@ -1,4 +1,4 @@
-<!-- $NetBSD: fixes.xml,v 1.29 2005/09/02 19:12:37 rillig Exp $ -->
+<!-- $NetBSD: fixes.xml,v 1.30 2005/09/14 16:46:13 reed Exp $ -->
<chapter id="fixes"> <?dbhtml filename="fixes.html"?>
<title>Notes on fixes for packages</title>
@@ -120,12 +120,13 @@
<para>Your package may depend on some other package being present
- and there are various ways of expressing this
dependency. pkgsrc supports the <varname>BUILD_DEPENDS</varname>
- and <varname>DEPENDS</varname> definitions, as well as
+ and <varname>DEPENDS</varname> definitions, the
+ <varname>USE_TOOLS</varname> definition, as well as
dependencies via <filename>buildlink3.mk</filename>, which is
the preferred way to handle dependencies, and which uses the
variables named above. See <xref linkend="buildlink"/> for more
information.</para>
-
+
<para>The basic difference between the two variables is as
follows: The <varname>DEPENDS</varname> definition registers
that pre-requisite in the binary package so it will be pulled in