gop alternatives and similar packages
Based on the "Package Management" category.
Alternatively, view gop alternatives based on common mentions on social networks and blogs.
dep9.8 1.6 gop VS depGo dependency tool.
glide9.5 0.0 gop VS glidePackage Management for Golang
godep9.4 0.0 gop VS godepdependency tool for go, godep helps build packages reproducibly by fixing their dependencies.
govendor9.3 0.4 gop VS govendorGo Package Manager. Go vendor tool that works with the standard vendor file.
gopm8.7 0.0 gop VS gopmGo Package Manager
gom7.9 0.0 gop VS gomGo Manager - bundle for go
virtualgo7.7 0.0 gop VS virtualgoVirtualgo: Easy and powerful workspace based development for go
gpm7.6 0.0 gop VS gpmBarebones dependency manager for Go.
gvt7.3 0.0 gop VS gvtgvt is a simple vendoring tool made for Go native vendoring (aka GO15VENDOREXPERIMENT), based on gb-vendor.
goop7.1 0.0 gop VS goopA simple dependency manager for Go (golang), inspired by Bundler.
MANUL6.9 0.0 gop VS MANUL:smirk_cat: The madness vendoring utility for Golang programs
modgv6.3 0.0 gop VS modgvConverts 'go mod graph' output into Graphviz's DOT language
Trash6.1 0.0 gop VS TrashMinimalistic Go vendored code manager
nut5.4 0.0 gop VS nutVendor Go dependencies
johnny-deps5.4 0.0 gop VS johnny-depsBarebones dependency manager for Go.
gigo5.3 0.0 gop VS gigoPIP-like dependency tool for golang, with support for private repositories and hashes.
mvn-golang5.2 4.6 gop VS mvn-golangmaven plugin to automate GoSDK load and build of projects
gup5.0 0.0 gop VS gupgup - Update binaries installed by "go install" with goroutines.
VenGO4.6 0.0 gop VS VenGOCreate and manage Isolated Virtual Environments for Go
go modulesModules are the unit of source code interchange and versioning. The go command has direct support for working with modules, including recording and resolving dependencies on other modules.
ONLYOFFICE Docs — document collaboration in your environment
Do you think we are missing an alternative of gop or a related project?
GOP is a project manangement tool for building your golang applications out of global GOPATH. In fact gop will keep both global GOPATH and every project GOPATH. But that means your project will not go-getable. Of course, GOP itself is go-getable. GOP copy all denpendencies from global GOPATH to your project's
src/vendor directory and all application's sources are also in
A normal process using gop is below:
git clone [email protected]:bac/aaa.git cd aaa gop ensure -g gop build gop test
- GOPATH compitable
- Multiple build targets support
- Put your projects out of global GOPATH
Please ensure you have installed the
go command, GOP will invoke it on building or testing
go get github.com/lunny/gop
Every project should have a GOPATH directory structure and put a
gop.yml int the root directory. This is an example project's directory tree.
<project root> ├── gop.yml ├── bin ├── doc └── src ├── main │ └── main.go ├── models │ └── models.go ├── routes │ └── routes.go └── vendor └── github.com ├── go-xorm │ ├── builder │ ├── core │ └── xorm └── lunny ├── log └── tango
Gop will recognize a gop project which has
gop.yml. The file is also a project configuration file. Below is an example. If you didn't define any target, the default target is src/main and the target name is the project name.
targets: - name: myproject1 dir: main assets: - templates - public - config.ini - key.pem - cert.pem - name: myproject2 dir: web assets: - templates - public - config.ini monitors: - config.ini
Create the default directory structure tree.
mkdir newproject cd newproject gop init
and you can also create config file for vscode
gop init -e=vscode
Automatically copy dependencies from $GOPATH to local project directory.
-g will let you automatically call
go get <package> when the package is missing on
-u will always
go get <package> on all the dependencies and copy them to
gop ensure [-g|-u] [target_name]
List all dependencies of this project and show the status.
gop status [target_name]
Add one or more packages to this project.
gop add <package1> <package2>
Update one or more packages to this project. All missing dependent packages will also be added. -f will update exists dependent packages.
gop update [-f] <package1> <package2>
Remove one or more packages from this project.
gop rm <package1> <package2>
go build on the src directory. If you want to execute ensure before build, you can use
gop build [-e] [target_name]
go run on the src directory.
-w will monitor the go source code changes and
automatically build and run again.
-e will automatically execute
ensure before every time build.
gop run [-w] [target_name]
go test on the src directory. If you want to execute ensure before build, you can use
gop test [-e] [target_name]
go release on the src directory.
gop release [target_name]
- [ ] Versions support, specify a dependency package verison
- [ ] Support run