Re:Ubuntu 18.04: Unity is gone, Gnome is back, and Ubuntu ha...
by teddyh on Thursday May 10, 2018 @11:49AM
(#17039965)
> Snaps avoid conflicts by having each app contain it's dependencies, which could otherwise conflict.
It also negates the entire point of having a package management system, as you can’t upgrade a security issue in libfoo and get it fixed once, but have to wait for all the users of libfoo, and the users of users of libfoo, and so on, to provide a new version of the Snap package with a new fixed libfoo contained inside it.
Re:Ubuntu 18.04: Unity is gone, Gnome is back, and Ubuntu ha...
by evand on Thursday May 10, 2018 @12:54PM
(#17040622)
I work for Canonical, but I also share maintainership of some snaps. From an automatic email I received recently:
“A scan of this snap shows that it was built with packages from the Ubuntu archive that have since received security updates. The following lists new USNs for affected binary packages in each snap revision:
…
Simply rebuilding the snap will pull in the new security updates and resolve this. If your snap also contains vendored code, now might be a good time to review it for any needed updates.“
Yes, you don’t get that library update everywhere all at once, but this gives each vendor a chance to make sure that update actually works with their app.
>> broken dependencies.
Not that it's Synaptic's fault, but some packages will have conflicting dependencies, especially if you're using PPA's to get recent software versions. It's not uncommon to get "foo (latest) requires bar >=3.1 but you have bar 2.8 installed. Baz (installed) requires bar 2.8". Snaps avoid conflicts by having each app contain it's dependencies, which could otherwise conflict.