apt/apt-pkg/cachefilter-patterns.cc, branch 2.1.2 Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=2.1.2 2020-03-10T09:57:21Z Don't crash pattern matching sections if pkg has no section 2020-03-10T09:57:21Z David Kalnischkies david@kalnischkies.de 2020-03-10T09:46:56Z urn:sha1:429effb963fba7529b8ff57d6b0474916d4fed69 Packages from third-party sources do not always follow the established patterns of more properly maintained archives. In that case it was a driver package for a scanner&printer device which has only a minimum of info attached, but also minimal non-installed packages do not include sections, so we really shouldn't assume their availability. patterns: test for empty terms, reject them 2020-02-03T11:55:54Z Julian Andres Klode julian.klode@canonical.com 2020-02-03T11:15:07Z urn:sha1:404771d0ec11f26a0b631018719e2918a049455b Correctly stop parsing short form arguments on space, also on ? 2020-02-03T11:55:54Z Julian Andres Klode julian.klode@canonical.com 2020-02-01T16:33:08Z urn:sha1:11a40ab11f72f85e905bdba4d3274870fbcaeaee we have to stop parsing on space so that things like ~ramd64 | ~rall work correctly. aptitude does not stop parsing on ?, but we'll do as it gets very confusing otherwise if you write stuff like ~ramd64?name(foo), and it resolves to ?and(?architecture(amd64?name), (foo))... patterns: Implement parsing of (...) groups 2020-02-03T11:55:54Z Julian Andres Klode julian.klode@canonical.com 2020-02-01T16:21:40Z urn:sha1:8886ea163032fb8bf64211a94c5dc252a4572a9c Implement | as or 2020-02-03T11:55:54Z Julian Andres Klode julian.klode@canonical.com 2020-02-01T16:12:35Z urn:sha1:d6f38436a229dc4421e77b58bf42d07bdb28b808 patterns: Allow rendering patterns as patterns instead of json-ish 2020-02-03T11:55:54Z Julian Andres Klode julian.klode@canonical.com 2020-02-01T16:11:19Z urn:sha1:cfec457d599373e6014b1f4472f48d5f989d76a5 patterns: Parse sequence of patterns as ?and 2020-02-03T11:55:54Z Julian Andres Klode julian.klode@canonical.com 2020-01-28T21:38:46Z urn:sha1:250119362e44599aad7e75462fa4298ad1ab1ad9 patterns: Allow bare words only in arguments 2020-02-03T11:55:54Z Julian Andres Klode julian.klode@canonical.com 2020-01-28T22:06:08Z urn:sha1:ebe5f39bfbb64921d5d31e0a6e49287356a5e6e2 This changes the syntax from approximately expr = unary unary = '!'? primary primary = pattern | short-pattern | word | quoted-word pattern = '?' name [ '(' expr [',' expr]* ')' ] short-pattern = ~ name | ~name expr to: primary = pattern | short-pattern argument = word | quoted-word | expr pattern = '?' name [ '(' argument [',' argument]* ')' ] short-pattern = ~ name | ~name argument patterns: Implement unary ! 2020-02-03T11:55:54Z Julian Andres Klode julian.klode@canonical.com 2020-01-28T20:46:10Z urn:sha1:8d4967d3a187dd66cf14b070a9db63f8ea21b21f Implement short patterns (patterns starting with ~) 2020-02-03T11:55:54Z Julian Andres Klode julian.klode@canonical.com 2020-01-20T13:14:49Z urn:sha1:fd43b1694f1382a3a47f5dc546ebe3d39fcd6e7d Also make pattern detector in cacheset and private's list accept such patterns. We probably should just try to parse and see if it is a (start of a) pattern.