A 'classic' snap is OK in the cases where the tool in question really, really makes sense as part of a classic environment. Things like compilers, editors, file viewers, etc, all make sense. It's also a nice comfortable way to start out making a snap, but for things that can be confined, its best not to stop at 'classic' and keep going to 'strict' via 'devmode' :)
The absence of confinement on classic snaps means we'll want to think carefully about how they end up on a user's system. At the moment our thinking is that they should ideally be: * built from upstream source * built on the same system that builds debs today If that's true, then we're really just cutting out a lot of work between upstream and distro users, not creating substantial new risks. To get a classic snap into the store you need to ask, and the folks there are expected to exercise judgment. Once we have a clear framework that works well, that will become policy. Its a lot of fun to make a snap, and upstreams that are not part of the Great Linux Tribal Theater are ime happy to see snapcraft.yaml land in their trunk so they get daily builds in edge channels for free from build.snapcraft.io. Those builds are created in the same trusted environment that debs are built. I would recommend it for places where you are working with upstreams that are fast moving (or where the 16.04 deb is out of date for other reasons). Mark -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
