This thread received relatively negative feedback on the use of hwpacks along Android/ChromeOS images. I think we should defer this part, at least we have more experience with said images.
I do agree with the overall approach of doing things in the upsteam way. I'm less clear on how end-users will consume these images from Linaro, we can revisit these questions if we reach the point where we need new tools to manipulate these images. (I'll remove the linux_image field from the spec) On Thu, Jan 20, 2011, Scott Bambrough wrote: > I have to jump in here. Hardware packs for Android or ChromeOS seem > ridiculous to me. If we want to be accepted by mainstream developers > for these OS, then we need to conform to the accepted norm for that > community. Imposing hardware packs in these two projects is just likely > to get our efforts ignored. On Thu, Jan 20, 2011, Patrik Ryd wrote: > I agree with Scott. > > There is no such thing in Android. The Android build system creates a number > of images. A boot image (depending of configuration), a system image and a > user data image. A hardware pack would probably be a subset of the boot and > system image. It would be hard to introduce a hardware pack for Android > without doing major changes. We should not fork Android and become a new > Android distribution. We should try to be as close to AOSP as possible. -- Loïc Minier _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
