Snappy and Ubuntu Desktop

Oliver Grawert ogra at
Tue Apr 21 10:49:02 UTC 2015

Am Dienstag, den 21.04.2015, 11:24 +0100 schrieb Nick McCloud:
> Snaps are all standalone and in theory, are ring fenced off from other snaps, so everything you need to get a desktop running would need to be in the one snap. It’s designed this way to prevent dependancies breaking thereby increasing reliability & confidence in deployment. So each snap includes any frameworks it wants in its bundle.
> My understanding of the project is that having a full desktop environment is not a use case it is designed. If you could get a snap together that had a desktop environment in it, it would be mighty similar to an LTS release with additional controls on the update mechanism.
pretty much the exact opposite is the case, snappy is the future of
Ubuntu everywhere (even on the desktop) ... if we say Convergence we
actually mean that you run *exactly* the same OS on *all* devices.
Convergence isn't just "uuh, my app adapts to a different form
factor" ;) 

ubuntu-core is simply the smallest common denominator all snappy
installs will have in common, from embedded over desktop to cloud
installs, which is why this was used for the initial snappy setup.

for the use cases robert and dider describe we have the framework
concept ... snaps can depend on frameworks ....

i.e. in the request above i would define:

- CUPS framework (to be re-used in all desktop snaps)
- Mir framework 
- XMir framework (for legacy apps, but not inside the Mir framework so
low end phones and embedded installscan drop it)
- Indeed our SDK framework used by Unity8
- an "ubuntu desktop support" framework with things like avahi, bluez,
ibus, zeitgeist etc as needed by unity8 ... this is something to split
into smaller pieces later imho.

... and one snap with the whole desktop itself on top ...


More information about the snappy-devel mailing list