> > > >> 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.
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. > > 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. > recipes intentionally don't require root privileges. That's a good thing. In a > past life (MeeGo?) I had package installs running as root in a chroot mess up > my bind-mounted /dev filesystem, affecting the host. > Luckily that never caused permanent damage. Agree, but this good thing doesn't come for free. See above points. Regards, Ed --------------------------------------------------------------------- Intel Finland Oy Registered Address: PL 281, 00181 Helsinki Business Identity Code: 0357606 - 4 Domiciled in Helsinki This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
