apt/apt-pkg/cachefilter-patterns.h, branch 3.1.1

refactor obsolete checks to use VerFileIterator::Downloadable()

2025-03-03T10:21:55Z

Add missing #include

2025-02-15T15:57:45Z

BaseRegexMatcher: Use std::optional [ABI]

2025-02-14T18:45:12Z

Add pkgCache::{Priority,DepType}_NoL10n to avoid duplication

2025-01-05T22:16:08Z

We don't have many places, but lets reduce the amount of duplicating these short strings, so that we may find all the places we have to change if that ever happens.

patterns: Safely peek ahead one byte

2024-11-18T18:23:01Z

The pattern tree parser was written using string_views in a no-copy fashion. However, at various places we assume that we can index one byte after the end of the string_view and get a NUL-byte there. This works fine in practice because we only ever pass it zero-terminated string_views, but it fails if you compile with -Wp,-D_GLIBCXX_ASSERTIONS because it will do bounds checks. So instead, do our own bounds checks here and always return '\0' if requesting one byte too many. Reported-by: Christian Heusel

apt-pkg/cachefilter-patterns.h, apt-pkg/cachefilter-patterns.cc: prepare for APT::StringView -> std::string_view

2024-11-12T19:36:19Z

Modernize standard library includes

2024-02-20T12:49:04Z

This was automated with sed and git-clang-format, and then I had to fix up the top of policy.cc by hand as git-clang-format accidentally indented it by two spaces.

Add the ?security pattern

2024-02-13T13:28:06Z

Add a new ?phasing pattern

2024-02-13T13:28:06Z

This selects all packages that are being kept back due to phasing on your system.

make ?installed pattern match installed version only when narrowed

2023-01-13T11:27:55Z

This is the correct behavior, but it was overlooked when aptitude patterns where ported. I remember wondering about this, but I checked the aptitude code and saw a check that CurrentVer != 0 or something and then apparently did not notice another implementation for version matching.