Notes:
- The experience of snapping a GTK application is similarly complicated as prior to bases.
- Missing libraries are not automatically pulled in from the host anymore, instead a list of what is missing is displayed, this may be too long a list for a big stack, library pulling might make sense to re-enable (explicitly or implicitly TBD) taking into account that some of these libraries may be provided by use of a snap leveraging the
contentinterface Simple trick to reduce size and startup time of GNOME-based snaps - GTK requires domain specific knowledge which the desktop parts encode (https://github.com/ubuntu/snapcraft-desktop-helpers), without that it requires one to be a GTK expert.
- Most of the GTK/GNOME tweaks are related to libraries living within /snap/…/usr and not / … some of these things could be just patched upstream or in the Ubuntu archive to consider snaps out of the box.
- ALSA is complicated, an extension would be ideal.
- overuse of stage-packages when using the content interface brings in duplicate content as there is no easy way to cut the dependency chain on stage-packages (this is why I built alsa, libsndfile and libportaudiocpp from source).