On 12-12-16 16:20, Robert P. J. Day wrote:
I always make a top-level git repository for the project. It contains all the "meta" layers as submodules (sometimes nested).
That way, the version of the top layer is the version of the whole product and can be reproduced any time.
in addition to all of the layers involved in the build, one has toThe only way to version such a system is to actually dump the whole package version table (e.g. "opkg list-installed"). You could compare the table to the initially installed one and only send the difference, as an optimization.
what sort of meaningful "version number" can be applied to somethingVersion "numbers" are for marketing purposes only and have no useful meaning in version management. The git hash is the "technical" version number. Create a table somewhere to map the commercial version number to a git hash. The simplest implementation is to "tag" the version numbers in the top-level repository.
Materiaalweg 4, NL-5681 RJ Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
Please consider the environment before printing this e-mail