distribution/version/version.go

package version

// Package is the overall, canonical project import path under which the
// package was built.
var Package = "github.com/docker/distribution"

// Version indicates which version of the binary is running. This is set to
// the latest release tag by hand, always suffixed by "+unknown". During
// build, it will be replaced by the actual version. The value here will be
// used if the registry is run after a go get based install.
var Version = "v2.1.0+unknown"
Report version in registry binary We've added support to the registry command to report the current version of the distribution package. The version package is generated with a shell script that gets the latest tag and add "+unknown". This allows builds from "go get" and "go install" to have a rough version number. Generated periodically, it will provide a decent indication of what code built the binary. For more accurate versioning, one can build with the "binaries" make target. Linker flags are used to replace the version string with the actual current tag at build time. Signed-off-by: Stephen J Day <stephen.day@docker.com> 2015-01-29 15:32:49 -08:00			`package version`

			`// Package is the overall, canonical project import path under which the`
			`// package was built.`
			`var Package = "github.com/docker/distribution"`

			`// Version indicates which version of the binary is running. This is set to`
			`// the latest release tag by hand, always suffixed by "+unknown". During`
			`// build, it will be replaced by the actual version. The value here will be`
			`// used if the registry is run after a go get based install.`
Rev base version to 2.1.0 Now that we've tagged a release candidate, we can now say all builds are "2.1.0+unknown" if the makefile is not used. Signed-off-by: Stephen J Day <stephen.day@docker.com> 2015-08-06 17:21:03 -07:00			`var Version = "v2.1.0+unknown"`