Vendor legacy snapcraft to maintain backward compatibility
Metadata
Current evaluation
Closed without implementation. The proposal to vendor legacy snapcraft for backward compatibility was abandoned or superseded by newer architecture, receiving no further discussion or action.
Suggested action: —
No scores available.
Issue body
The introduction of bases breaks backward compatibility. Rather than actually break backward compatibility in the snap, the legacy snapcraft should be vendored and the snapcraft snap should dispatch between new and legacy depending on the usage of bases.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed without implementation. The proposal to vendor legacy snapcraft for backward compatibility was abandoned or superseded by newer architecture, receiving no further discussion or action. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without implementation. The proposal to vendor legacy snapcraft for backward compatibility was abandoned. No comments or resolution details were provided, indicating the approach was likely superseded by later snapcraft architecture changes. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without implementation. The proposal to vendor legacy snapcraft for backward compatibility was abandoned or superseded by alternative compatibility measures. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Vendoring legacy snapcraft to maintain backward compatibility was closed without implementation. Zero comments indicate the suggestion was abandoned. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #2285 snapcraft snap: vendor legacy snapcraft | snapcraft | merged | Merged. Vendored legacy snapcraft into the snapcraft snap to resolve LP: #1793261, maintaining support when no base is specified in snapcraft.yaml. Approved by one reviewer and passed CI checks prior to integration. | |
| #1659085 snapcraft needs to migrate to a snap directory | snapcraft (launchpad) | closed | Closed without resolution. The proposed migration of snapcraft to a snap directory, including build artifact relocation and plugin updates, was abandoned or superseded by subsequent architecture changes. | |
| #1551716 snapcraft does not allow vendor/platform patching of upstream sources (aka: add patch phase to lifecycle) | snapcraft (launchpad) | closed | Abandoned and closed without implementation. The requested patch lifecycle phase was never added to snapcraft. Vendor patching remains unsupported, requiring manual workarounds or source forks. | |
| #4194 Migrate snapcraft_legacy subcommands to use craft-cli | snapcraft | closed | Abandoned. The maintainer rejected the proposed approach, confirming the legacy CLI handler will remain in use short-term while commands are fully migrated out of snapcraft_legacy in the medium term. | |
| #1548225 Snapcraft/snappy should detect incompatible version mismatches | snapcraft (launchpad) | closed | Abandoned. The report detailed Snapcraft failing to detect version mismatches, causing large snaps to install incorrectly. With zero comments and over a decade of dormancy, it received no resolution and was closed. | |
| #5754 Remove the `snapcraftctl` compatibility wrapper | snapcraft | closed | Abandoned. Maintainers closed the request to remove the snapcraftctl compatibility wrapper, retaining it to prevent breaking existing builds for core22 and core24. | |
| #1666908 Create a snapcraft snap | snapcraft (launchpad) | closed | Closed without implementation. The request to package snapcraft as a snap was abandoned after nearly a decade with no comments or follow-up action. |