[pkgsrc/trunk]: pkgsrc/doc/guide/files Mention USE_TOOLS also may express a d...

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

details:   https://anonhg.NetBSD.org/pkgsrc/rev/1a55cb65759f
branches:  trunk
changeset: 499216:1a55cb65759f
user:      reed <reed%pkgsrc.org@localhost>
date:      Wed Sep 14 16:46:13 2005 +0000

description:
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:

 doc/guide/files/fixes.xml |  7 ++++---
 1 files changed, 4 insertions(+), 3 deletions(-)

diffs (25 lines):

diff -r aa98f32d21fb -r 1a55cb65759f doc/guide/files/fixes.xml
--- a/doc/guide/files/fixes.xml Wed Sep 14 16:44:12 2005 +0000
+++ b/doc/guide/files/fixes.xml Wed Sep 14 16:46:13 2005 +0000
@@ -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