tdnf installonly_limit implementation behavioral parity with DNF
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- C
- Stars
- 130
- Forks
- 55
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 7
Description
Is your feature request related to a problem? Please describe.
TDNF is removing package by least recent installation, while DNF is by lower package version.
https://github.com/oliverkurth/tdnf/blob/8c73a0e825e5e14496c30a3ccfb829aeaf019749/client/goal.c#L1104-L1105
Example showing the behavior discrepancy between TDNF and DNF:
Describe the solution you'd like
It would be optimal to be in parity with DNF to that regards.
Describe alternatives you've considered
n/a
Additional context
n/a
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in client/goal.c around lines 1104-1105, where the issue identifies the current installonly_limit behavior. Compare that selection with DNF's lower-package-version behavior and use the linked example as the behavioral reference. Done means TDNF removes packages according to the same rule as DNF.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100