Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-05-23 08:58:41 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 111

Removing glide instructions from building code docs (#1217)

Browse source 
I think these were useful when none of us knew how to use glide except
@groob and needed copy-pasteable commands to run, but this seems like
it's much less useful now.
This commit is contained in:
Mike Arpaia 2017-02-14 13:16:16 -07:00 committed by GitHub
parent 545961ad5b
commit e8f1285364
1 changed files with 0 additions and 15 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
docs/development/building-the-code.md
View file

@ -60,18 +60,3 @@ make build
It's not necessary to use Make to build the code, but using Make allows us to account for cross-platform differences more effectively than the `go build` tool when writing automated tooling. Use whichever you prefer.
## Managing Go Dependencies with Glide
[Glide](https://github.com/Masterminds/glide#glide-vendor-package-management-for-golang) is a package manager for third party Go libraries. See the ["How It Works"](https://github.com/Masterminds/glide#how-it-works) section in the Glide README for full details.
### Installing the correct versions of dependencies
To install the correct versions of third package libraries, use `glide install`. `glide install` will use the `glide.lock` file to pull vendored packages from remote vcs. `make deps` takes care of this step, as well as downloading the latest version of glide for you.
### Adding new dependencies
To add a new dependency, use [`glide get [package name]`](https://github.com/Masterminds/glide#glide-get-package-name)
### Updating dependencies
To update, use [`glide up`](https://github.com/Masterminds/glide#glide-update-aliased-to-up) which will use VCS and `glide.yaml` to figure out the correct updates.