Op 31 dec. 2011, om 09:10 heeft Robert Yang het volgende geschreven: > Incremental image generation, the rootfs would be totally removed and > re-created in the second generation by default, but with INC_IMAGE_GEN = > "1", the rootfs would be kept, and will do update(remove/add some pkgs) > on it. > NOTE: This is not suggested when you want to create a productive rootfs > > For example: > 1) Add the follow config option to a conf file: > INC_IMAGE_GEN = "1" > > 2) bitbake core-image-sato > modify a package > bitbake core-image-sato > > The rootfs would not be totally removed and re-created in the second > generation, it would be simply updated based on the "package". > > Implatation: > 1) Figure out the pkg which need to be removed or re-installed, then use > 'rpm -e to remove the old one. Use the rpm's BUILDTIME to determine > which pkg has been rebuilt. > > 2) Figure out the pkg which is newly added, and use 'rpm -U' to install > it. > > This only for the rpm based rootfs, I don't know whether we also need > this for ipk or deb based rootfs.
If you insist on calling it "INC_IMAGE_GEN" then yes, you need to implement it for every package format.
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
