I'm probably misunderstanding. Are you saying that the behavior of "snapcraft snap <directory>" is completely different from the behavior of "cd <directory>; snapcraft snap"?
On Wed, May 18, 2016 at 10:42 AM, Kyle Fazzari <kyle.fazz...@canonical.com> wrote: > On 05/18/2016 09:07 AM, Yann Sionneau wrote: > > So now maybe I'm thinking this is normal behavior and if I'm choosing to > > just do "snapcraft snap <DIRECTORY>" then it means the <directory> > > should already be containing "everything". > > Which means I should generate myself the shell wrappers that snapcraft > > generates when doing "snapcraft build" ? > > Indeed, if you're running `snapcraft snap <directory>` snapcraft doesn't > do anything for you other than call mksquashfs, which means that you > need to have it all ready to go (along with any wrappers, the meta/ > directory, etc.). This is expected behavior. > > -- > Kyle Fazzari (kyrofa) > Software Engineer > Canonical Ltd. > k...@canonical.com > > > -- > snappy-devel mailing list > snappy-devel@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/snappy-devel > > -- gustavo @ http://niemeyer.net
-- snappy-devel mailing list snappy-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snappy-devel
