One the major drawbacks of Snapcraft (for me) is, that it cannot provide me, afaik, with a complete set of licenses of all the dependencies that are used to build a snap or are contained in a snap. Therefore, in my company, I may not use any snap provided by Canonical or someone else or cannot even build my own, as during build Snapcraft loads all the neccessary dependencies from some Canonical server (I won’t even talk about my struggles to use snapcraft with our company proxy…).
Despite Canonicals voluminous promises “We help you keep track of the licenses you depend on.” snappy is basically useless when going to production, at least in our company.
A snap build via Snapcraft would never survive our open source clearing.
We have used Yocto in some prior projects, and Yocto CAN provide a complete list of all the used open source software used and can even integrate license texts or source code into a package or image, if required by a license used during build.
So the best solution might be, to use the Yocto build framework to build a snap.
There is already a Yocto recipe to build snapd for Yocto. Perhaps someone already tinkered around to use Yocto to build a snap?
Are there perhaps any endeavours under way at Canonical?