`autoversion` gives version based on most recent tag - not latest version

[JedMeister]

Running autoversion on a repo will build the version from the most recent tag, not the version considered the "latest". That means that the version output of autoversion may be different than the latest package built by pool. E.g. with a git history that look like this:

48fc4049 And even more updated
8f9bf18a (tag: v2.0.0) More updates
fa45c689 (tag: v2.1.0) Updates

$ autoversion
2.0.0+1-g48fc4049

whereas

$ pool-list PACKAGE
PACKAGE=2.1.0+2-g48fc4049

IMO autoversion should give the latest version - not a version calculated from the latest tag - i.e. consistent with what pool gives you. Perhaps there is a case for also being able to give the version based on the most recent tag, but IMO by default it should give the same version as pool would build.

My rationale is that I often use autoversion to test versions, but because it bases the version on the latest tag I have been caught out by using malformed version tags which either result in pool buing packages with an unexpected version or (if the version is specified) a package version that will not install (the version is considered older than the version already installed).

Perhaps autoversion should even have the ability to generate a version tag?