This very minor issue arises during Debian packaging, where some Debian Go package maintainers prefer packaging from a release tarball with a nice version number, e.g.
golang-github-spf13-afero (0.10.0-1)
rather than a placeholder version "0.0" like this:
golang-github-spf13-afero (0.0~git20151126.0.12fcb8c-1)
I personally don't mind either way, but fellow Debian Go package maintainer @tianon, who packaged blackfriday for Debian, prefers packaging from tagged releases, e.g.:
and then I broke his pattern when I uploaded a new version because Hugo depends on blackfriday's new feature:
So @tianon urged me to nudge @russross to tag a release v1.3: russross/blackfriday#198 so he can upload a new version with a nice version number:
And ditto for v1.4, haha.
git describe
) :-)
docker
and hugo
can be built "reproducibly", with all the dependencies already inside the Debian biosphere, and without accessing the Internet during build time.
go get
or git clone
during a Debian package build run.
It's also nice that unlike some of my other libraries (hugo, cobra, viper) it Googles very well.
Looks like the name just got some competition ;)
http://techcrunch.com/2015/12/16/afero-uncloaks/ and http://www.afero.io/