How to reasonably create multiple overlays
For the squashfs (ro rootfs), isar-cip-core just has one overlay (/etc), but in some specific case, the downstream met some issues and have to create more overlay (such as, /var, /ca/certs, etc.), so is there the better way to create multiple overlay paths?
For example, creating a overlay class or a .inc file which just takes the lower and the upper-path as parameters. And then, it just fills in the values in templates and installs the files accordingly.
Currently, only the downstream project can solve this problem by own, but if the upstream (isar-cip-core) can provide the better solution, all of downstreams can benefit from that.
Edited by jundong liu