[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openembedded-core
Subject:    [OE-core] [PATCH 1/2] V2 Incremental image generation(rpm based rootfs)
From:       koen () dominion ! thruhere ! net (Koen Kooi)
Date:       2011-12-31 8:48:54
Message-ID: 62EA68FF-FDFA-4F2A-B7EF-DEE961ED47AE () dominion ! thruhere ! net
[Download RAW message or body]


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.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 203 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://layers.openembedded.org/pipermail/openembedded-core/attachments/20111231/bba9de29/attachment.sig>



[prev in list] [next in list] [prev in thread] [next in thread]