On 2018-02-05 19:47, Russel Winder wrote:
Clearly the Dub workflow is all about using Git. However other workflows builds from a release tarball so there is no use of git commands in such a situation. So for example, Debian packaging happens from release tarballs.
I actually think it's kind of annoying that Dub ties a Git tag to a new
version of the Dub package. I might not want to release a new Dub
package for every Git tag. At the same time "git describe" is very useful.
The simplest thing to do is probably to have the version specified in a
separate file that included with the "import" expression. One would
build a small tool/script to also create a Git tag by reading this file.
/Jacob Carlborg