summaryrefslogtreecommitdiff
path: root/doc/apt-patterns.7.xml
Commit message (Collapse)AuthorAgeFilesLines
* apt-patterns(7): Grouping with () and or using | are supportedJulian Andres Klode2023-01-131-4/+0
| | | | They have been since 1.9.9, lol
* make ?installed pattern match installed version only when narrowedJulian Andres Klode2023-01-131-1/+4
| | | | | | | | 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.
* Release 2.3.142.3.14Julian Andres Klode2022-01-061-1/+1
|
* add pattern to select packages by codename (closes: #1002646)Johannes Schauer Marin Rodrigues2021-12-261-0/+3
|
* Release 2.3.102.3.10Julian Andres Klode2021-10-181-1/+1
|
* add pattern to select packages by priority (closes: #989558)Johannes Schauer Marin Rodrigues2021-10-041-0/+3
|
* Release 2.1.172.1.17Julian Andres Klode2021-01-111-1/+1
|
* Fixup manual page docbook syntaxJulian Andres Klode2021-01-081-4/+4
| | | | | | | No idea why we don't have manual page syntax check (what prepare-release post-build does) in CI. Should fix that eventually. Gbp-Dch: ignore
* Implement ?reverse-depends/~R and friendsJulian Andres Klode2020-12-271-0/+8
| | | | This was easy.
* woofJulian Andres Klode2020-12-271-1/+1
|
* patterns: Add dependency patterns ?depends, ?conflicts, etc.Julian Andres Klode2020-12-271-0/+19
| | | | | | These match the target package, not target versions which is slightly unfortunate but might make sense. Maybe we should add a version that matches Versions instead.
* Fix "string match{ing,es}" and whitespace typo in apt-patterns(7)Chris Leick2020-04-051-2/+2
|
* Release 1.9.91.9.9Julian Andres Klode2020-02-041-1/+1
|
* apt-patterns(7): Document | operator, (), and add an exampleJulian Andres Klode2020-02-041-1/+7
| | | | Missed that in pu/short-patterns.
* apt-patterns(7): Some updates and rationaleJulian Andres Klode2020-02-031-3/+10
|
* patterns: Parse sequence of patterns as ?andJulian Andres Klode2020-02-031-1/+1
|
* patterns: Implement unary !Julian Andres Klode2020-02-031-1/+1
|
* Implement short patterns (patterns starting with ~)Julian Andres Klode2020-02-031-18/+18
| | | | | | 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.
* Release 1.9.51.9.5Julian Andres Klode2019-12-021-1/+1
|
* patterns: Add ?sectionJulian Andres Klode2019-11-261-0/+3
|
* patterns: Add ?all-versionsJulian Andres Klode2019-11-261-0/+3
|
* patterns: Implement ?narrow(...), as ?any-version(?and(...))Julian Andres Klode2019-11-261-0/+6
| | | | | This is pure syntactic sugar - ?narrow does not exist in the abstract syntax.
* patterns: Add ?any-versionJulian Andres Klode2019-11-261-0/+11
|
* patterns: Add ?originJulian Andres Klode2019-11-251-0/+3
|
* patterns: Add ?archiveJulian Andres Klode2019-11-251-0/+3
|
* patterns: Add ?source-name and ?source-versionJulian Andres Klode2019-11-251-0/+6
|
* patterns: Add ?versionJulian Andres Klode2019-11-251-0/+11
|
* Add ?virtual patternJulian Andres Klode2019-08-151-0/+5
| | | | This matches any package that does not have versions.
* Add the ?exact-name patternJulian Andres Klode2019-08-151-0/+3
| | | | | | The ?exact-name pattern matches the name exactly, there is no substring matching going on, or any regular expression or fnmatch magic.
* Add ?essential patternJulian Andres Klode2019-08-151-0/+3
| | | | | | This matches all packages where at least one of the versions is marked essential; or well, whenver apt considers a package essential.
* Add ?broken patternJulian Andres Klode2019-08-151-0/+3
| | | | | This matches all packages that have broken dependencies in the installed version or the version selected for install.
* Add ?config-files and ?installed patternsJulian Andres Klode2019-08-151-0/+9
| | | | | | These two are mutually exclusive states of installed-ness. And ?installed package is fully unpacked and configured; a ?config-files package only has config files left.
* Add ?obsolete and ?upgradable patternsJulian Andres Klode2019-08-151-0/+6
| | | | | | | | | These match packages that have no version in a repository, or where an upgrade is available. Notably, ?and(?obsolete,?upgradable) == ?false because an upgradable package is by definition not obsolete.
* Add ?automatic and ?garbage patternsJulian Andres Klode2019-08-151-0/+11
| | | | | | These patterns allow you to identify automatically installed packages, as well as automatically installed packages that are no longer reachable from the manually installed ones.
* Add patterns for the existing CacheFilter::Matcher classesJulian Andres Klode2019-08-151-2/+36
| | | | | | | This implements the basic logic patterns: ?and ?false ?not ?or ?true and the basic package patterns: ?architecture ?name ?x-name-fnmatch
* doc: Add apt-patterns(7) manual pageJulian Andres Klode2019-08-151-0/+87
This does not describe much yet, as there's not much to talk about.
generated by cgit v1.2.3-70-g09d2 (git 2.46.0) at 2024-11-01 03:38:37 +0000