X-Git-Url: https://git.saurik.com/apt.git/blobdiff_plain/245dde96193702f7f51389d3583dee547f8ba366..864fe99c3628585ba2081650e441ab15e4ee7bae:/doc/apt.conf.5.xml
diff --git a/doc/apt.conf.5.xml b/doc/apt.conf.5.xml
index 7d5f7e9b3..920b42ba1 100644
--- a/doc/apt.conf.5.xml
+++ b/doc/apt.conf.5.xml
@@ -301,6 +301,8 @@ DPkg::Pre-Install-Pkgs {"/usr/sbin/dpkg-preconfigure --apt";};
Valid-Until header, but if they don't or a
stricter value is desired the Max-ValidTime
option below can be used.
+ The option of &sources-list; entries should be
+ preferred to disable the check selectively instead of using this global override.
@@ -312,7 +314,8 @@ DPkg::Pre-Install-Pkgs {"/usr/sbin/dpkg-preconfigure --apt";};
the earlier date of the two is used as the expiration date.
The default value is 0 which stands for "valid forever".
Archive specific settings can be made by appending the label of the archive
- to the option name.
+ to the option name. Preferably, the same can be achieved for specific
+ &sources-list; entries by using the option there.
@@ -324,7 +327,8 @@ DPkg::Pre-Install-Pkgs {"/usr/sbin/dpkg-preconfigure --apt";};
frequently updated archive with a Valid-Until header
instead of completely disabling the expiration date checking.
Archive specific settings can and should be used by appending the label of
- the archive to the option name.
+ the archive to the option name. Preferably, the same can be achieved for specific
+ &sources-list; entries by using the option there.
@@ -593,6 +597,15 @@ DPkg::Pre-Install-Pkgs {"/usr/sbin/dpkg-preconfigure --apt";};
+
+
+ This option controls if apt will use the DNS SRV server record
+ as specified in RFC 2782 to select an alternative server to
+ connect to.
+ The default is "true".
+
+
+
Allow the update operation to load data files from
@@ -686,7 +699,7 @@ DPkg::Pre-Install-Pkgs {"/usr/sbin/dpkg-preconfigure --apt";};
The configuration item RootDir has a special
- meaning. If set, all paths in Dir:: will be
+ meaning. If set, all paths will be
relative to RootDir, even paths that
are specified absolutely. So, for instance, if
RootDir is set to
@@ -695,6 +708,7 @@ DPkg::Pre-Install-Pkgs {"/usr/sbin/dpkg-preconfigure --apt";};
/var/lib/dpkg/status, then the status file
will be looked up in
/tmp/staging/var/lib/dpkg/status.
+ If you want to prefix only relative paths, set Dir instead.
@@ -770,10 +784,34 @@ DPkg::Pre-Install-Pkgs {"/usr/sbin/dpkg-preconfigure --apt";};
install to the commands, one per line on the requested file descriptor, defaulting
to standard input.
- Version 2 of this protocol dumps more information, including the
- protocol version, the APT configuration space and the packages, files
- and versions being changed. Version 3 adds the architecture and MultiArch
- flag to each version being dumped.
+ Version 2 of this protocol sends more information through the requested
+ file descriptor: a line with the text VERSION 2,
+ the APT configuration space, and a list of package actions with filename
+ and version information.
+
+ Each configuration directive line has the form
+ key=value. Special characters (equal signs, newlines,
+ nonprintable characters, quotation marks, and percent signs in
+ key and newlines, nonprintable characters, and percent
+ signs in value) are %-encoded. Lists are represented
+ by multiple key::=value lines with the same key. The
+ configuration section ends with a blank line.
+
+ Package action lines consist of five fields in Version 2: old version, direction
+ of version change (< for upgrades, > for downgrades, = for no
+ change), new version, action. The version fields are "-" for no version
+ at all (for example when installing a package for the first time; no
+ version is treated as earlier than any real version, so that is an
+ upgrade, indicated as - < 1.23.4). The action field
+ is "**CONFIGURE**" if the package is being configured, "**REMOVE**" if it
+ is being removed, or the filename of a .deb file if it is being
+ unpacked.
+
+ In Version 3 after each version field follows the architecture
+ of this version, which is "-" if there is no version, and a field showing
+ the MultiArch type "same", foreign", "allowed" or "none". Note that "none"
+ is an incorrect typename which is just kept to remain compatible, it
+ should be read as "no" and users are encouraged to support both.The version of the protocol to be used for the command
cmd can be chosen by setting