Documentation
¶
Overview ¶
Package buildinfo reports which build of vexscan is running.
It reads what the Go toolchain already stamps into the binary rather than taking a version from -ldflags, so a plain `go install github.com/cwayne18/vexscan@v0.6.2` self-describes exactly as a release build does. There is nothing to keep in sync and nothing to forget to pass.
Every part is best effort and none of it is invented. A binary built by `go build` from a checkout reports "(devel)" and a dirty tree is marked as such -- those are the honest answers, not gaps to paper over, and a bug report that says "(devel)-dirty" has told the reader something true.
Index ¶
Constants ¶
const Name = "vexscan"
Name is the tool's own name, so the report descriptor and the --version line spell it the same way.
Variables ¶
This section is empty.
Functions ¶
func Revision ¶
func Revision() string
Revision is the short commit the binary was built from, suffixed "-dirty" when the tree had uncommitted changes. Empty when the build carried no VCS stamp at all, which is what happens inside `go test`.
func Short ¶
func Short() string
Short is the provenance stamp a report carries: "vexscan v0.6.2 (a1b2c3d)", or just "vexscan v0.6.2" when there is no revision left to add.
Types ¶
This section is empty.
Source Files