Paul Gevers wrote:
> The security line in your APT configuration may look like:
> <programlisting>deb https://deb.debian.org/debian-security
> bullseye-security main contrib</programlisting>
> </para>
> + <para>
> + If APT is configured using APT pinning or
> + <literal>APT::Default-Release</literal>,
"Configured using" is a bit unclear; I think you mean
If your APT configuration also involves pinning or
<literal>APT::Default-Release</literal>,
(I'm assuming APT::Default-Release users will be aware they're doing
it, presumably because they've got sources defined for more than one
release and need to specify which one is "primary")
> the configuration
> + most likely need updating as the codename of the security
"is likely to need updating", or:
it is likely to
require adjustments as the codename of the security
> + archive no longer matches that of the regular archive. An
> + example of a working <literal>APT::Default-Release</literal>
> + line for bullseye looks:
line for bullseye looks like:
> + <programlisting>APT::Default-Release
> "/^bullseye(|-security|-upgrades)$/";</programlisting>
> + which takes advantage of the undocumented feature of APT that
> + it supports POSIX fnmatch patterns and regular expressions
> + (inside <literal>/</literal>).
> + </para>
Do we need to mention fnmatch patterns (AKA globs) when the example
doesn't use them? Even if we do, we should make it clearer that
"inside /" only means regexps:
it supports regular expressions (inside <literal>/</literal>)
as well as glob patterns.
(Or should "glob" be in quotes, or <literal>s?)
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
