New image organization and snap format

Oliver Grawert ogra at
Mon Jan 11 09:04:03 UTC 2016

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>
> 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).

as i said before that only becomes a prob in larger scale, i'm not sure
how many officially supported sub-arches we plan to have in the future.

alternatively we could indeed rename the kernel packages and have them
have the right name from the start (though i imagine that will cause a
lot of probs for -generic which is used in other context everywhere in
the distro) 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 173 bytes
Desc: This is a digitally signed message part
URL: <>

More information about the snappy-devel mailing list