Snapcraft needs better state tracking
Metadata
Current evaluation
Closed without implementation. The proposed refactoring for improved per-part state tracking was not pursued, likely superseded by later architectural changes or abandoned.
Suggested action: —
No scores available.
Issue body
Currently Snapcraft keeps track of the last-run step by saving it in a state file per part. In order to serve future state improvements, this needs to be refactored to include data per state per part.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed without implementation. The proposed refactoring for improved per-part state tracking was not pursued, likely superseded by later architectural changes or abandoned. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without implementation. The proposed state tracking refactor was not addressed, likely abandoned or superseded by subsequent Snapcraft development. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1560158 Migrate old Snapcraft state tracking to new | snapcraft (launchpad) | closed | Closed without resolution or comments. The legacy state tracking migration request appears abandoned or superseded by subsequent Snapcraft updates. No fix or merge was recorded. | |
| #1778081 Snapcraft saves the fact that parts need to be rebuilt rather than discovering them | snapcraft (launchpad) | closed | Closed without implementation. The dynamic dependency discovery approach for build caching was abandoned and superseded by later Snapcraft caching architecture updates. |