It was <2014-12-08 pon 17:22>, when Bartosh, Eduard wrote: >>>>> MIC is a tool I like least. Partly because (which is not mic's >>>>> fault) current image configuration is spread between IMHO too many >>>>> packages and in the end one needs to extract ks files manually >>>>> from an RPM. >>>> >>>> At the moment we still need MIC for full Tizen images. Yocto as it >>>> stands today can build images, but does not offer all the features >>>> that MIC has. >>> >>> Like? >> >> Last I heard, ext4 support and installing certain kinds of boot >> loaders were problematic. But I haven't been involved much; Ed >> Bartosh can say more. >> > extlinux requires root privileges to be able to install itself on the > image. Yocto imager only supports syslinux and FAT boot partitions.
That is not a great limitation, is it? I'll try to look why syslinux needs less privileges. > Regarding image configuration. From my point of view we should drop > current complicated scheme of generation image-configurations, put .ks > files into image-configuration and start maintaining it the same way > as other packages. It will be much cleaner and maintainable. I might be missing something but do .ks files support any kind of layers? I don't know if it's absolutely necessary but I like the idea of having some parts of the configuration common to many profiles and some parts profile specific. >> > It looks like there is nothing a proper recipe can't do that MIC can. > It can't run %post scripts natively. Which is quite serious restriction. Indeed. %post scripts need to be designed to run on a build host. That makes conversion between bb and spec (both ways) a bit of a problem, doesn't it? -- Łukasz Stelmach Samsung R&D Institute Poland Samsung Electronics
pgprBtroXmN8A.pgp
Description: PGP signature
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
