diff options
| author | Julian Andres Klode <julian.klode@canonical.com> | 2020-01-28 23:41:54 +0100 |
|---|---|---|
| committer | Julian Andres Klode <julian.klode@canonical.com> | 2020-02-03 12:55:54 +0100 |
| commit | 775be4274e5c5427079e26d3ebe3c7f2f5f6b76a (patch) | |
| tree | 288ae1edf8b9fffc76782a7ff4a8ef3c1c4f6b9b | |
| parent | 250119362e44599aad7e75462fa4298ad1ab1ad9 (diff) | |
apt-patterns(7): Some updates and rationale
| -rw-r--r-- | doc/apt-patterns.7.xml | 13 |
1 files changed, 10 insertions, 3 deletions
diff --git a/doc/apt-patterns.7.xml b/doc/apt-patterns.7.xml index 3de9b00fc..6fa945058 100644 --- a/doc/apt-patterns.7.xml +++ b/doc/apt-patterns.7.xml @@ -168,9 +168,6 @@ </para> <itemizedlist> <listitem> - <para>Only long forms — the ones starting with ? — are supported</para> - </listitem> - <listitem> <para> Syntax is uniform: If there is an opening parenthesis after a term, it is always assumed to be the beginning of an argument list. </para> @@ -193,6 +190,16 @@ <listitem> <para>?narrow accepts infinite arguments</para> </listitem> + <listitem> + <para><code>foo</code> cannot be used as a shortform for <code>?name(foo)</code>, as this can cause typos to go unnoticed: + Consider <code>?and(...,~poptional)</code>: + this requires the package to have <code>required</code> priority, but + 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> </itemizedlist> </refsect1> |