On 24.09.24 16:41, Shengjing Zhu wrote:
The reason that I propose to use 0.0~gitYYYYMMDD is to just track the latest commit in the mono repo. It just stops caring how the sub modules are tagged and avoid confusing in the single packaging version This is what I have done for golang-github-moby-sys-dev package which has similar mono repo that contains many sub modules.
At the end of the day, I don't really care what the Debian package version number is. If it's 0.0~gitYYYYMMDD, then it is super easy to adopt a different scheme later (i.e., if the upstream developers come to their senses), as virtually any other version number style will be greater than 0.0~git...
What's more important is that it contains the specific upstream code that other packages are urgently depending on to move forward. I would however suggest that we at least record the upstream versions somewhere obvious, e.g. as a d/changelog entry, to make our jobs as packagers a little easier.
I intensely dislike mono repos.
OpenPGP_signature.asc
Description: OpenPGP digital signature
