New image organization and snap format
sergio.schvezov at canonical.com
Mon Jan 11 13:36:21 UTC 2016
On Mon, Jan 11, 2016 at 6:04 AM, Oliver Grawert <ogra at ubuntu.com> wrote:
> Am Sonntag, den 10.01.2016, 15:20 -0200 schrieb Martin Albisetti:
> > On Sat, Jan 9, 2016 at 10:48 AM, Oliver Grawert <ogra at ubuntu.com>
> > wrote:
> > >
> > > not naming them after their actual content (linux-generic, linux
> > > -raspi2)
> > > means that you need to maintain mapping between the names if you
> > > want to
> > > do automated builds (your build system needs to know that pi2-linux
> > > needs to contain the linux-raspi2 device bits) ....
> > The gadget snap will specify which snaps are needed in for that
> > gadget, including the kernel and OS.
> > That should solve it, right?
> well, it still needs to know how to generate the canonical-pi2-linux
> snap first ... if that info can be obtained from the gadget snap the
> build system would need to know how to obtain that snap and how to
> extract the necessary info from it (vs using a name that has been used
> in former stages and can just be handed through from stage to stage
> like we do everywhere else up to today).
I thought the list of snaps was going to come from the model assertion.
Martin can you double check just in case?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the snappy-devel