X-Git-Url: https://git.saurik.com/apt.git/blobdiff_plain/9c4e6026c498078aa223eae95f2c9752cb45525c..864fe99c3628585ba2081650e441ab15e4ee7bae:/doc/apt.conf.5.xml
diff --git a/doc/apt.conf.5.xml b/doc/apt.conf.5.xml
index 0f98a6fe9..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.
@@ -586,6 +590,74 @@ DPkg::Pre-Install-Pkgs {"/usr/sbin/dpkg-preconfigure --apt";};
+
+
+ The maximum file size of Release/Release.gpg/InRelease files.
+ The default is 10MB.
+
+
+
+
+
+ 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
+ a repository without a trusted signature. If enabled this
+ option no data files will be loaded and the update
+ operation fails with a error for this source. The default
+ is false for backward compatibility. This will be changed
+ in the future.
+
+
+
+
+
+ Allow that a repository that was previously gpg signed to become
+ unsigned durign a update operation. When there is no valid signature
+ of a perviously trusted repository apt will refuse the update. This
+ option can be used to override this protection. You almost certainly
+ never want to enable this. The default is false.
+
+ Note that apt will still consider packages from this source
+ untrusted and warn about them if you try to install
+ them.
+
+
+
+ scope
+
+ Acquiring changelogs can only be done if an URI is known from where to get them.
+ Preferable the Release file indicates this in a 'Changelogs' field. If this isn't
+ available the Label/Origin field of the Release file is used to check if a
+ Acquire::Changelogs::URI::Label::LABEL or
+ Acquire::Changelogs::URI::Origin::ORIGIN option
+ exists and if so this value is taken. The value in the Release file can be overridden
+ with Acquire::Changelogs::URI::Override::Label::LABEL
+ or Acquire::Changelogs::URI::Override::Origin::ORIGIN.
+
+ The value should be a normal URI to a text file, expect that package specific data is
+ replaced with the placeholder CHANGEPATH. The
+ value for it is: 1. if the package is from a component (e.g. main)
+ this is the first part otherwise it is omitted, 2. the first letter of source package name,
+ expect if the source package name starts with 'lib' in which case it will
+ be the first four letters. 3. The complete source package name. 4. the complete name again and
+ 5. the source version.
+ The first (if present), second, third and fourth part are separated by a slash ('/')
+ and between the fourth and fifth part is an underscore ('_').
+
+ The special value 'no' is available for this option indicating that
+ this source can't be used to acquire changelog files from. Another source will be tried
+ if available in this case.
+
+
+
@@ -627,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
@@ -636,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.
@@ -711,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