Tue Dec 24 15:29:44 2013 UTC ()
Missing documentation update for the new default behaviour of "FETCH_USING".


(tron)
diff -r1.48 -r1.49 pkgsrc/doc/guide/files/faq.xml
cvs diff -r1.48 -r1.49 pkgsrc/doc/guide/files/faq.xml (expand / switch to unified diff)

--- pkgsrc/doc/guide/files/faq.xml 2011/07/31 08:48:22 1.48
+++ pkgsrc/doc/guide/files/faq.xml 2013/12/24 15:29:44 1.49
@@ -1,14 +1,14 @@ @@ -1,14 +1,14 @@
1<!-- $NetBSD: faq.xml,v 1.48 2011/07/31 08:48:22 spz Exp $ --> 1<!-- $NetBSD: faq.xml,v 1.49 2013/12/24 15:29:44 tron Exp $ -->
2 2
3<chapter id="faq"> <?dbhtml filename="faq.html"?> 3<chapter id="faq"> <?dbhtml filename="faq.html"?>
4<title>Frequently Asked Questions</title> 4<title>Frequently Asked Questions</title>
5 5
6<para>This section contains hints, tips &amp; tricks on special things in 6<para>This section contains hints, tips &amp; tricks on special things in
7pkgsrc that we didn't find a better place for in the previous chapters, and 7pkgsrc that we didn't find a better place for in the previous chapters, and
8it contains items for both pkgsrc users and developers.</para> 8it contains items for both pkgsrc users and developers.</para>
9 9
10<!-- ================================================================== --> 10<!-- ================================================================== -->
11 11
12 <sect1 id="mailing-list-pointers"> 12 <sect1 id="mailing-list-pointers">
13 <title>Are there any mailing lists for pkg-related discussion?</title> 13 <title>Are there any mailing lists for pkg-related discussion?</title>
14 14
@@ -262,27 +262,27 @@ that allow finer tuning of the tree layo @@ -262,27 +262,27 @@ that allow finer tuning of the tree layo
262 262
263<!-- ================================================================== --> 263<!-- ================================================================== -->
264 264
265<sect1 id="resume-transfers"> 265<sect1 id="resume-transfers">
266<title>How to resume transfers when fetching distfiles?</title> 266<title>How to resume transfers when fetching distfiles?</title>
267 267
268<para>By default, resuming transfers in pkgsrc is disabled, but you can 268<para>By default, resuming transfers in pkgsrc is disabled, but you can
269enable this feature by adding the option 269enable this feature by adding the option
270<varname>PKG_RESUME_TRANSFERS=YES</varname> into 270<varname>PKG_RESUME_TRANSFERS=YES</varname> into
271&mk.conf;. If, during a fetch step, an incomplete 271&mk.conf;. If, during a fetch step, an incomplete
272distfile is found, pkgsrc will try to resume it.</para> 272distfile is found, pkgsrc will try to resume it.</para>
273 273
274<para>You can also 274<para>You can also
275use a different program than the default &man.ftp.1; by changing the 275use a different program than the platform default program by changing the
276<varname>FETCH_USING</varname> variable. You can specify the program by 276<varname>FETCH_USING</varname> variable. You can specify the program by
277using of ftp, fetch, wget or curl. Alternatively, fetching can be disabled 277using of ftp, fetch, wget or curl. Alternatively, fetching can be disabled
278by using the value manual. A value of custom disables the system defaults 278by using the value manual. A value of custom disables the system defaults
279and dependency tracking for the fetch program. In that case you have to 279and dependency tracking for the fetch program. In that case you have to
280provide <varname>FETCH_CMD</varname>, <varname>FETCH_BEFORE_ARGS</varname>, 280provide <varname>FETCH_CMD</varname>, <varname>FETCH_BEFORE_ARGS</varname>,
281<varname>FETCH_RESUME_ARGS</varname>, <varname>FETCH_OUTPUT_ARGS</varname>, 281<varname>FETCH_RESUME_ARGS</varname>, <varname>FETCH_OUTPUT_ARGS</varname>,
282<varname>FETCH_AFTER_ARGS</varname>.</para> 282<varname>FETCH_AFTER_ARGS</varname>.</para>
283 283
284<para>For example, if you want to use 284<para>For example, if you want to use
285<filename>wget</filename> to download, you'll have to use something 285<filename>wget</filename> to download, you'll have to use something
286like:</para> 286like:</para>
287 287
288<programlisting> 288<programlisting>