snap.yaml change landed
lefteris at slock.it
Thu Jan 28 14:45:01 UTC 2016
> Just for clarification, snapcraft does not support frameworks since 2.0
Hm this scares me. I just noticed I am using snapcraft version 0.5. So far
I am building the framework I am working on via snapcraft. Here is a guide
I wrote about it:
and also a link to the snapcraft yaml file:
How can I do the same with newer snapcraft versions?
Technical Lead at slock.it <http://www.slock.it>
Twitter <https://twitter.com/LefterisJP>, Github
<https://github.com/LefterisJP>, Blog <http://blog.refu.co>
On Thu, Jan 28, 2016 at 3:31 PM, Michael Vogt <michael.vogt at canonical.com>
> On Thu, Jan 28, 2016 at 10:43:25AM -0300, Sergio Schvezov wrote:
> > El 28/01/16 a las 10:19, Michael Vogt escribió:
> > > As the skills system evolves the security handling will be
> > > This will be announced here.
> > In the case of snapcraft, skills are not implemented. This is all rather
> new. So I guess that if the previous way of declaring security related bits
> is no longer valid, all snapcraft created snaps are also currently going to
> be broken.
> Indeed, sorry for this. The migration-skill syntax is done in a way
> that makes it very easy to port existing snaps. But of course it still
> need some tweaks in snapcraft.
> > > Note that "frameworks" are supported currently in the meta/snap.yaml
> > > to make the transition easier. These will eventually be handled via
> > > skills as well.
> > Just for clarification, snapcraft does not support frameworks since 2.0
> Interessting. Snappy still has the code mostly because we need it to
> keep docker/owncloud working until the skills/capabilities have
> evoloved enough to support this fully.
> snappy-devel mailing list
> snappy-devel at lists.ubuntu.com
> Modify settings or unsubscribe at:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the snappy-devel