Using package managers in these languages you can define the use of a dependency, in a file, and a supported version range (e.g.,
>= 1.2.3, < 2.0.0 or in shorthand as
^1.2.3). To have consistent reproducible builds you can also pin to specific versions. Glide now supports this ability.
Glide 0.8.0 adds a
glide.lock file. This file, generated when
glide update is run, contains the entire dependency tree and the commit id for each dependency. This includes the complete dependency tree which means dependencies of dependencies or dependencies and so on. It’s also smart enough to get the version information from Godep, GPM, and GB when those configuration files are available. We recommend storing the
glide.lock file in your VCS alongside your
To install what’s defined in the
glide.lock file you can run
glide install. This operation is fairly fast as fetching updates and setting versions uses concurrency to speed up the process. It’s also smart enough to make sure the lockfile is a match for the
glide.yaml file so they don’t get out of sync.
glide.lock file exists the
glide install command runs
For more details on the other changes see the release notes.