summaryrefslogtreecommitdiff
path: root/doc/apt-patterns.7.xml
diff options
context:
space:
mode:
authorJulian Andres Klode <jak@debian.org>2023-01-13 16:54:41 +0000
committerJulian Andres Klode <jak@debian.org>2023-01-13 16:54:41 +0000
commit0970d6407f53be34c54dbab5db0f29e961899f73 (patch)
treed48fe4e20c34e30259c8d2ef4af9c45ff81efbc5 /doc/apt-patterns.7.xml
parent5919d2d18eac6e445a59da23246df94258e103eb (diff)
parent9a29ea6f6d0f9115044c0ccddde3dc6454d483da (diff)
Merge branch 'pu/installed-matches-version' into 'main'
make ?installed pattern match installed version only when narrowed See merge request apt-team/apt!275
Diffstat (limited to 'doc/apt-patterns.7.xml')
-rw-r--r--doc/apt-patterns.7.xml9
1 files changed, 4 insertions, 5 deletions
diff --git a/doc/apt-patterns.7.xml b/doc/apt-patterns.7.xml
index 45f2f9fd7..9d4f0a94e 100644
--- a/doc/apt-patterns.7.xml
+++ b/doc/apt-patterns.7.xml
@@ -108,7 +108,7 @@
<listitem><para>Selects packages that can be removed automatically.</para></listitem>
</varlistentry>
<varlistentry><term><code>?installed</code></term><term><code>~i</code></term>
- <listitem><para>Selects packages that are currently installed.</para></listitem>
+ <listitem><para>Selects packages that are currently installed. Since version 2.5.4, narrowing this pattern (see narrowing patterns above) makes it only match installed versions (see version patterns below).</para></listitem>
</varlistentry>
<varlistentry><term><code>?name(REGEX)</code></term><term><code>~nREGEX</code></term>
<listitem><para>Selects packages where the name matches the given regular expression.</para></listitem>
@@ -138,6 +138,9 @@
<varlistentry><term><code>?codename(REGEX)</code></term>
<listitem><para>Selects versions that come from the codename that matches the specified regular expression. Codename, here, means the values after <code>n=</code> in <command>apt-cache policy</command>.</para></listitem>
</varlistentry>
+ <varlistentry><term><code>?installed</code></term><term><code>~i</code></term>
+ <listitem><para>Selects package versions that are currently installed. Versions prior to 2.5.4 only matched at the package level, hence <code>?any-version(?installed?version(2.0))</code>matched even if 2.0 was not installed, but another version was.</para></listitem>
+ </varlistentry>
<varlistentry><term><code>?origin(REGEX)</code></term><term><code>~OREGEX</code></term>
<listitem><para>Selects versions that come from the origin that matches the specified regular expression. Origin, here, means the values after <code>o=</code> in <command>apt-cache policy</command>.</para></listitem>
</varlistentry>
@@ -233,10 +236,6 @@
if you do not type the <code>~</code>, it would require the package name to contain <code>poptional</code>.</para>
</listitem>
<listitem>
- <para>Grouping patterns with <code>(...)</code> or writing <code>?or(A,B)</code> as <code>A|B</code> are not supported. We
- do not believe that the use of <code>|</code> is that common, and the grouping is not necessary without it.</para>
- </listitem>
- <listitem>
<para>Dependency types for ~D and related operators need to be specified in the canonical case.</para>
</listitem>
</itemizedlist>