On 2017-02-15 18:33, Geoffrey Levillain wrote:
Hi,
These patches introduce a capability to install overlay into image after
fetching them.
There is actually a need to add image-specific configurations files into
image recipes, and these patches are a way to standardize this process as
well as simplify it by re-enabling fetching when image_overlay is
inherited, and by providing a task that copy every files in directories
listed in OVERLAY_ROOT_DIRS into IMAGE_ROOTFS directory.
Geoffrey Levillain (3):
image.bbclass: No need to force image licence on MIT
image_overlay.bbclass: Add possibility to install overlays to image
rm_work.bbclass: Do not remove fetching and install_overlay stamps
meta/classes/image.bbclass | 2 +-
meta/classes/image_overlay.bbclass | 24 ++++++++++++++++++++++++
meta/classes/rm_work.bbclass | 4 ++++
3 files changed, 29 insertions(+), 1 deletion(-)
create mode 100644 meta/classes/image_overlay.bbclass
Can you give an example where this approach is better than just
having the image include some [possibly optional] packages that
contain these image-specific configuration files?
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core