Wed Jan 2 18:48:21 2019 UTC ()
guide: adjust example for BUILD_DEPENDS


(tnn)
diff -r1.146 -r1.147 pkgsrc/doc/guide/files/fixes.xml
cvs diff -r1.146 -r1.147 pkgsrc/doc/guide/files/fixes.xml (expand / switch to unified diff)

--- pkgsrc/doc/guide/files/fixes.xml 2018/09/10 12:10:53 1.146
+++ pkgsrc/doc/guide/files/fixes.xml 2019/01/02 18:48:21 1.147
@@ -1,14 +1,14 @@ @@ -1,14 +1,14 @@
1<!-- $NetBSD: fixes.xml,v 1.146 2018/09/10 12:10:53 leot Exp $ --> 1<!-- $NetBSD: fixes.xml,v 1.147 2019/01/02 18:48:21 tnn Exp $ -->
2 2
3<chapter id="fixes"> <?dbhtml filename="fixes.html"?> 3<chapter id="fixes"> <?dbhtml filename="fixes.html"?>
4<title>Making your package work</title> 4<title>Making your package work</title>
5 5
6<sect1 id="general-operation"> 6<sect1 id="general-operation">
7 <title>General operation</title> 7 <title>General operation</title>
8 8
9 <para>One appealing feature of pkgsrc is that it runs on many 9 <para>One appealing feature of pkgsrc is that it runs on many
10 different platforms. As a result, it is important to ensure, 10 different platforms. As a result, it is important to ensure,
11 where possible, that packages in pkgsrc are portable. This 11 where possible, that packages in pkgsrc are portable. This
12 chapter mentions some particular details you should pay 12 chapter mentions some particular details you should pay
13 attention to while working on pkgsrc.</para> 13 attention to while working on pkgsrc.</para>
14 14
@@ -339,27 +339,27 @@ ACCEPTABLE_LICENSES+=xv-license @@ -339,27 +339,27 @@ ACCEPTABLE_LICENSES+=xv-license
339.include "../../graphics/jpeg/buildlink3.mk" 339.include "../../graphics/jpeg/buildlink3.mk"
340</programlisting> 340</programlisting>
341 <para>but set 341 <para>but set
342 <varname>BUILDLINK_DEPMETHOD.<replaceable>jpeg</replaceable>?=build</varname> 342 <varname>BUILDLINK_DEPMETHOD.<replaceable>jpeg</replaceable>?=build</varname>
343 to make it a build dependency only. This case is rather 343 to make it a build dependency only. This case is rather
344 rare.</para> 344 rare.</para>
345 </listitem> 345 </listitem>
346 346
347 <listitem> 347 <listitem>
348 <para>If your package needs binaries from another package to build, 348 <para>If your package needs binaries from another package to build,
349 use the <varname>BUILD_DEPENDS</varname> definition:</para> 349 use the <varname>BUILD_DEPENDS</varname> definition:</para>
350 350
351<programlisting> 351<programlisting>
352BUILD_DEPENDS+= scons-[0-9]*:../../devel/scons 352BUILD_DEPENDS+= itstool-[0-9]*:../../textproc/itstool
353</programlisting> 353</programlisting>
354 </listitem> 354 </listitem>
355 355
356 <listitem> 356 <listitem>
357 <para>If your package needs a library with which to link and 357 <para>If your package needs a library with which to link and
358 there is no <filename>buildlink3.mk</filename> file 358 there is no <filename>buildlink3.mk</filename> file
359 available, create one. Using 359 available, create one. Using
360 <varname>DEPENDS</varname> won't be sufficient because the 360 <varname>DEPENDS</varname> won't be sufficient because the
361 include files and libraries will be hidden from the compiler.</para> 361 include files and libraries will be hidden from the compiler.</para>
362 </listitem> 362 </listitem>
363 363
364 <listitem> 364 <listitem>
365 <para>If your package needs some executable to be able to run 365 <para>If your package needs some executable to be able to run