Chriss wrote:To describe the code someone refers to, the hash is perfect. BUT, for packaging, I need to have a version which can be ordered. I (or rather the package manager) need to know which package is newer, so I know when to update the package. The Git hash has no order. It is useless for that use case. For packaging, it is NOT sufficient.
This. And, when including the build number into the file name of installer packages, it's also far easier to tell which is the newer version. That's, after all, the whole point of build numbers being ordered.
So maybe a Build number could be "0.4.4+r<commit-count>.<git hash>"?
That wouldn't be a build number anymore, but a version number. Not exactly the same, a build number should identify a specific build all by itself, without the need to specify a version.
Not sure if the "+" works, as in: the relevant package managers understand that 0.4.4 < 0.4.4+ < 0.4.5.
With an ordered build number that's not part of a version number no problem at all.