engicam-stable / engicam-bsp-release Goto Github PK

Would it be possible for you to provide manifests where the revisions of all the meta layers (including the engicam meta layer) point to a specific commit id or tag?
For instance instead of:

<project name="meta-engicam-nxp" path="sources/meta-engicam-nxp" remote= "engicam" revision="hardknott"/>

you may provide something like:

<project name="meta-engicam-nxp" path="sources/meta-engicam-nxp" remote= "engicam" revision="4b668f781cb784d241298474bc10a183f895a386"/>

or even better:

<project name="meta-engicam-nxp" path="sources/meta-engicam-nxp" remote= "engicam" revision="refs/tags/rel_engicam_hardknott_1.0.0"/>

where rel_engicam_hardknott_1.0.0 would be a tag in the meta-engicam-nxp repository pointing to the latest released and tested commit of the hardknott branch.

This would reflect the approach used in NXP's released manifests and it would lead to consistent builds across time: e.g. if a released manifest builds a certain image today, ideally it should build the same exact image in the future.

The same approach should also be propagated to the inner recipes. For example in the meta-engicam-nxp layer, the linux kernel recipes point to the branch instead of pointing to a specific commit, like NXP's kernel recipe does.

I understand this would require more work in order to maintain version references, but it would definitely help to diagnose issues and work on stable builds.