In the KDE Neon 6 extension design, do the content snaps have ABI versioning or do they follow a design like the Gnome extension which updates libraries continually on the same content base? (Since GTK3 is frozen and GTK4 is backwards compatible, this works well for Gnome).
The reason I ask is because I vaguely remember (and could be mistaken) that in Core 22, KDE Neon consumer snaps had to be regularly rebuilt with the new content snaps or they’d become out of sync, is this true and if so, is it still the case?
I’d like to give KeepassXC a dependency bump but the project isn’t keen on snaps in general so I’m keen to see if this implementation is viable with longer term support commitments (e.g., say 6-18 months without a rebuild)
Thanks Scarlett, that covers the majority of the concern, I imagine then it’s a Gnome like model where the QT6 libs get upgraded across API in the same content snap but keep their binary level support which is great position to be in.
