Handling versioning of platform snaps
sergio.schvezov at canonical.com
Tue Mar 7 13:55:45 UTC 2017
On Tue, 7 Mar 2017 05:06:46 -0800, Mark Shuttleworth wrote:
> Hi Tim
> Welcome aboard, and thank you, this is exactly the type of question we
> want to be solving together on this list.
> The simplest approach would be to insert a major version/ABI indcation
> in the platform snap name. Something like lirios3 and lirios4 would be a
> very explicit way to provided different versions of your libraries. It
> would have the major benefit that both platform snaps could be installed
> at the same time, too, enabling a more natural app transition (each app
> can choose when to hop from 3 to 4) rather than a big-bang flag day for
> each device. The downside would be the incremental size of having both
> installed at once during that transition, but we continually see that
> 'time is more precious than disk space' so giving users a low-friction
> way to 'just work' is more useful than saving 0.2 GB of their 1 TB disk.
> It might be worth looking into the linking of apps to particular tracks,
> but this raises a lot of tricky questions that I suspect would be a
> swamp with more problems than solutions.
> Does that sound like a reasonable starting point?
This is what I suggested during the rocket chat conversations and I agree it is the best way to move forward. What is interesting here is (once there is support to bring in default slot implemetations for an interface), to garbage collect all the liriosX-1 snaps that are not connected to anything (or whatever number makes sense with rollbacks and current garbage collection rules).
Sent using Dekko from my Ubuntu device
More information about the Snapcraft