Hi Tom,
Let's back in this context. This is really important and I was waiting
to complete the previous stage.
Em 17-03-2014 13:11, Otavio Salvador escreveu:
If my understand is right, I like the feature. My only concern is
people overusing it and adding contents which are not 'tracked' in the
build system in a product release which seems attractive when we first
think about it but cause some management, tracking and authenticity
check problems in long term.
I don't know how to better address this from wic perspective. Usually
we end doing multiple images as part of the build process for those
special cases and I don't know how wic could be 'told' about those
secondary rootfs existence.
I have been working on it since Otavio's concerns about 'contents which
are not tracked'.
So extending my previous patches (80% done) to handle this situation is
quite easy. Like this:
bitbake directdisk-multi-image-e img1=core-image-minimal -e
img2=core-image-minimal -e img3=core-image-minimal
directdisk-multi-image.wks:
part /boot --source bootimg-pcbios --ondisk sda --fstype=msdos --label
boot --active --align 1024
part / --source rootfs --image-name=img1 --ondisk sda --fstype=ext3
--label primary --align 1024
part /standby --source rootfs --image-name=img2 --ondisk sda
--fstype=ext3 --label secondary --align 1024
part /root --source rootfs --image-name=img3 --ondisk sda --fstype=ext3
--label root_sec --align 1024
If the user put '--image-name' and '--rootfs-dir' the '--image-name'
takes precedence.
As wic is a generic tool, the user could prefer to use images from OE or
any other rootfs-dir.
Tom, what do you think? Could I go ahead?
Thanks
--
João Henrique Ferreira de Freitas - joaohf_at_gmail.com
Campinas-SP-Brasil
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
