Vendor legacy snapcraft to maintain backward compatibility
Bug #1793261 reported by
Kyle Fazzari
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| Snapcraft | Status tracked in Trunk | |||||
| Legacy |
Fix Committed
|
Medium
|
Kyle Fazzari | |||
| Trunk |
Fix Released
|
Medium
|
Kyle Fazzari | |||
Bug Description
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.
Revision history for this message
| Kyle Fazzari (kyrofa) wrote | #1 |
Revision history for this message
| Kyle Fazzari (kyrofa) wrote | #2 |
| Changed in snapcraft: | |
| status: | New → Fix Committed |
| milestone: | none → 2.44 |
| assignee: | nobody → Kyle Fazzari (kyrofa) |
| importance: | Undecided → Medium |
To post a comment you must log in.
This is a two step process. First of all, refactor build-override to reduce duplication: https:/