&apt-email;
&apt-product;
<!-- The last update date -->
- <date>2012-06-09T00:00:00Z</date>
+ <date>2015-12-14T00:00:00Z</date>
</refentryinfo>
<refmeta>
configuration list - in which case it will be silently ignored.</para></listitem>
<listitem><para>the main configuration file specified by
<literal>Dir::Etc::main</literal></para></listitem>
+ <listitem><para>all options set in the binary specific configuration
+ subtree are moved into the root of the tree.</para></listitem>
<listitem><para>the command line options are applied to override the
configuration directives or to load even more configuration files.</para></listitem>
</orderedlist>
<varlistentry><term><option>Default-Release</option></term>
<listitem><para>Default release to install packages from if more than one
version is available. Contains release name, codename or release version. Examples: 'stable', 'testing',
- 'unstable', '&stable-codename;', '&testing-codename;', '4.0', '5.0*'. See also &apt-preferences;.</para></listitem>
+ 'unstable', '&debian-stable-codename;', '&debian-testing-codename;', '4.0', '5.0*'. See also &apt-preferences;.</para></listitem>
</varlistentry>
<varlistentry><term><option>Ignore-Hold</option></term>
<listitem><para>
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
+ of a previously 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.
with <literal>Acquire::Changelogs::URI::Override::Label::<replaceable>LABEL</replaceable></literal>
or <literal>Acquire::Changelogs::URI::Override::Origin::<replaceable>ORIGIN</replaceable></literal>.
- The value should be a normal URI to a text file, expect that package specific data is
- replaced with the placeholder <literal>CHANGEPATH</literal>. The
+ The value should be a normal URI to a text file, except that package specific data is
+ replaced with the placeholder <literal>@CHANGEPATH@</literal>. The
value for it is: 1. if the package is from a component (e.g. <literal>main</literal>)
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 '<literal>lib</literal>' in which case it will
+ except if the source package name starts with '<literal>lib</literal>' 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 ('<literal>/</literal>')
</variablelist>
</refsect1>
+ <refsect1><title>Binary specific configuration</title>
+ <para>Especially with the introduction of the <command>apt</command> binary
+ it can be useful to set certain options only for a specific binary as
+ even options which look like they would effect only a certain binary like
+ <option>APT::Get::Show-Versions</option> effect
+ <command>apt-get</command> as well as <command>apt</command>.
+ </para>
+ <para>Setting an option for a specific binary only can be achieved by
+ setting the option inside the
+ <option>Binary::<replaceable>specific-binary</replaceable></option>
+ scope. Setting the option <option>APT::Get::Show-Versions</option> for
+ the <command>apt</command> only can e.g. by done by setting
+ <option>Binary::apt::APT::Get::Show-Versions</option> instead.</para>
+ <para>Note that as seen in the DESCRIPTION section further above you can't
+ set binary-specific options on the commandline itself nor in
+ configuration files loaded via the commandline.</para>
+ </refsect1>
+
<refsect1><title>Directories</title>
<para>The <literal>Dir::State</literal> section has directories that pertain to local
by multiple <literal>key::=value</literal> lines with the same key. The
configuration section ends with a blank line.</para>
- <para>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
+ <para>Package action lines consist of five fields in Version 2: package
+ name (without architecture qualification even if foreign), 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 <literal>- < 1.23.4</literal>). The action field
<para>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"
+ 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.</para>
projects / apt.git / blobdiff