On Thu, Apr 30, 2015 at 12:22 AM, Ash Charles <[email protected]> wrote: > On Sun, Apr 26, 2015 at 3:49 PM, Sergio Schvezov > <[email protected]> wrote: >> This just means that we require manual review on the store for oem packages >> because they are not confined by default. > Ah---makes sense. Either way, the package got approved so this did > the trick for me this morning :) > > sudo ubuntu-device-flash core -o overo.img --oem=gumstix-overo.ash 15.04 > <snip> >> oem packages are what you want, we have killed flashtool-assets with this >> generic way of enabling oems to wok with the ubuntu kernels in a way that >> enables them to focus on what matters to them, feel free to log bug reports >> (or reply here) with anything you think will make or would have made the oem >> enablement part a better experience for you. > I'd still need a device tarball ('--device-part' for udf) if I wanted > a different kernel correct?
yes, thats correct. oem snaps (or gadget snaps how we will call them in future) allow you to configure the kernel part, but not ship your own. you can however (as in case of our pi2 example) upload the oem snap to store and user just have to figure how and where to get the tarball for enablement. > > --Ash -- snappy-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snappy-devel
