> 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? It's a question to Tizen architects. It might influence boot time, which can be critical for some profiles like IVI.
> I'll try to look why syslinux needs less privileges. syslinux uses mtools for installation. ext4linux needs writeable block device to query block number(s) of secondary bootloader as far as I know. > > > 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. Yes, and that was the reason of designing current scheme. I'm not sure it worth the effort. I'd better live with some duplication than with the scheme where there is no way to get image configuration rather than from final rpm. just my 0.02$ > >> > 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? They also need to be designed to understand that root is in the directory, which is even more tricky. You can grep meta-tizen sources for [ "x$D" == "x" ] to see what I'm talking about. This is most common example: [ "x$D" == "x" ] && ldconfig This means that to convert rpm/deb package repository to this scheme all %post scripts have to be heavily modified. I'm not saying it's bad though. It's just how it is. Regards, Ed > -- > Łukasz Stelmach > Samsung R&D Institute Poland > Samsung Electronics --------------------------------------------------------------------- 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
