update/re-order the options docs
This commit is contained in:
parent
62d75ad3e1
commit
e01b01c579
|
@ -456,7 +456,7 @@ builtins.fetchurl {
|
||||||
|
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
||||||
<varlistentry xml:id="conf-negative-disk-cache-ttl"><term><literal>negative-disk-cache-ttl</literal></term>
|
<varlistentry xml:id="conf-narinfo-cache-negative-ttl"><term><literal>narinfo-cache-negative-ttl</literal></term>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
|
|
||||||
|
@ -469,6 +469,24 @@ builtins.fetchurl {
|
||||||
|
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
||||||
|
<varlistentry xml:id="conf-narinfo-cache-positive-ttl"><term><literal>narinfo-cache-positive-ttl</literal></term>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
|
||||||
|
<para>The TTL in seconds for positive lookups. If a store path is
|
||||||
|
queried from a substituter, the result of the query will be cached
|
||||||
|
in the local disk cache database including some of the NAR
|
||||||
|
metadata. The default TTL is a month, setting a shorter TTL for
|
||||||
|
positive lookups can be useful for binary caches that have
|
||||||
|
frequent garbage collection, in which case having a more frequent
|
||||||
|
cache invalidation would prevent trying to pull the path again and
|
||||||
|
failing with a hash mismatch if the build isn't reproducible.
|
||||||
|
</para>
|
||||||
|
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
</varlistentry>
|
||||||
|
|
||||||
<varlistentry xml:id="conf-netrc-file"><term><literal>netrc-file</literal></term>
|
<varlistentry xml:id="conf-netrc-file"><term><literal>netrc-file</literal></term>
|
||||||
|
|
||||||
<listitem><para>If set to an absolute path to a <filename>netrc</filename>
|
<listitem><para>If set to an absolute path to a <filename>netrc</filename>
|
||||||
|
@ -523,24 +541,6 @@ password <replaceable>my-password</replaceable>
|
||||||
|
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
||||||
<varlistentry xml:id="conf-positive-disk-cache-ttl"><term><literal>positive-disk-cache-ttl</literal></term>
|
|
||||||
|
|
||||||
<listitem>
|
|
||||||
|
|
||||||
<para>The TTL in seconds for positive lookups. If a store path is
|
|
||||||
queried from a substituter, the result of the query will be cached
|
|
||||||
in the local disk cache database including some of the NAR
|
|
||||||
metadata. The default TTL is a month, setting a shorter TTL for
|
|
||||||
positive lookups can be useful for binary caches that have
|
|
||||||
frequent garbage collection, in which case having a more frequent
|
|
||||||
cache invalidation would prevent trying to pull the path again and
|
|
||||||
failing with a hash mismatch if the build isn't reproducible.
|
|
||||||
</para>
|
|
||||||
|
|
||||||
</listitem>
|
|
||||||
|
|
||||||
</varlistentry>
|
|
||||||
|
|
||||||
<varlistentry xml:id="conf-pre-build-hook"><term><literal>pre-build-hook</literal></term>
|
<varlistentry xml:id="conf-pre-build-hook"><term><literal>pre-build-hook</literal></term>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
|
|
Loading…
Reference in a new issue