- Ensure 'best' architecture is choosen on fresh install [DONE]
- Ensure update keeps architecture [DONE]
- Ensure dist-upgrade chooses 'best' architecture
- Improve logging so solver decisions are comprehensible
- to support 'recommends'
- mark rules as 'weak' so trackback on assignment conflict can
- disable such rules and continue
- essentialfor, supplements
- will be almost for free when weak rules are implemented
- still rules have to be marked 'reverse' for logging and proposal
- correctness
- Define syntax for 'boolean expression' capability
- How to express and, or, not within a .spec file ?
- See 'extended reldeps' below
- support local(de), locale(de,at,ch) and locale(<package>:de)
- eventually extend 'package' to reldep, e.g. locale(package > 5.3-2:de)
- support modalias(<modalias-regexp>) and modalias(<package>:<modalias-regexp>)
- eventually extend 'package' to reldep, e.g. modalias(package >5.3-2:<modalias-regexp>)
- architecture-specific dependencies
- ability to keep packages at a specific version
- ability to prevent installation of specific packages / reldep
- Boolean AND, OR
- Compare architecture
- Compare namespace
- Two types of conjunctions:
- "a>5 AND b>5" => a and b can be provided by different solvables
- "a>5 WITH b>5" => 'and' operation but a and b are provided by same solvable. (the 'with' operator is a naming proposal)
- Full range of boolean operators (AND, OR, NOT) and conditionals (IF/THEN/ELSE) for dependencies.
- Prefer solvables from specific sources
- Support for package splits, renames
- if transactions are unsolvable, offer understandable proposals what to change to make the transaction solvable.
- compute all possible solutions and rank them
- configurable solution ranking
- best sources, newest packages, smallest download size,
- smallest install size, lowest number of installs, lowest number of
- updates, lowest number of removals, prefer most popular packages, prefer vendor,
