Created attachment 6185 [PATCH] configure.in.in: specify version in component form I based my changes on xfce4-panel's configure.ac.in file and verified that a correct version string is generated with both orage_version_tag set to 'git' and to an empty string.
Problem is that this way there is no way of knowning what is the order of versions because git tag has no order info. Compared to seq numbers like today, which grow.
You can still decide to bump the nano version everytime you make a commit to keep your 'seq numbers'. your call, but other xfce components use the same scheme to construct the version..
When doing 'git log configure.in.in' ideally I'd want to see actual changes and not version bumps. I sometimes do this when packaging a new version to see if there are dependency or other similar changes so I can tweak the flags passed to ./configure. This was my motivation when filing this issue (and writing the patch) though development is also made slightly more straightforward since there's no need to bump the version with each change. As far as I'm aware, there's no benefit to providing virtual version numbers that don't correspond to released tarballs. With the proposed patch, each development build is uniquely identified by the commit ID it was built from and this is sufficient to distinguish builds from each other. The order in which changes happen during development is not important for most (if not all) purposes. I'd really like to see this implemented but I could understand it being a matter of personal preference.
The orage project is not maintained anymore and has been archived. Closing bugs.