gigo alternatives and similar packages
Based on the "Package Management" category.
Alternatively, view gigo alternatives based on common mentions on social networks and blogs.
dep9.8 1.6 gigo VS depGo dependency tool.
glide9.5 0.0 gigo VS glidePackage Management for Golang
godep9.4 0.0 gigo VS godepdependency tool for go, godep helps build packages reproducibly by fixing their dependencies.
govendor9.3 0.4 gigo VS govendorGo Package Manager. Go vendor tool that works with the standard vendor file.
gopm8.7 0.0 gigo VS gopmGo Package Manager
gom7.9 0.0 gigo VS gomGo Manager - bundle for go
virtualgo7.7 0.0 gigo VS virtualgoVirtualgo: Easy and powerful workspace based development for go
gpm7.6 0.0 gigo VS gpmBarebones dependency manager for Go.
gvt7.3 0.0 gigo VS gvtgvt is a simple vendoring tool made for Go native vendoring (aka GO15VENDOREXPERIMENT), based on gb-vendor.
goop7.1 0.0 gigo VS goopA simple dependency manager for Go (golang), inspired by Bundler.
MANUL6.9 0.0 gigo VS MANUL:smirk_cat: The madness vendoring utility for Golang programs
modgv6.2 0.0 gigo VS modgvConverts 'go mod graph' output into Graphviz's DOT language
Trash6.1 0.0 gigo VS TrashMinimalistic Go vendored code manager
nut5.4 0.0 gigo VS nutVendor Go dependencies
johnny-deps5.4 0.0 gigo VS johnny-depsBarebones dependency manager for Go.
mvn-golang5.1 6.0 gigo VS mvn-golangmaven plugin to automate GoSDK load and build of projects
gup4.9 6.7 gigo VS gupgup - Update binaries installed by "go install" with goroutines.
VenGO4.7 0.0 gigo VS VenGOCreate and manage Isolated Virtual Environments for Go
gop3.5 0.0 gigo VS gopBuild and manage your Go applications out of GOPATH
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.
Static code analysis for 29 languages.
Do you think we are missing an alternative of gigo or a related project?
Fetching packages in golang can be difficult, especially when juggling multiple packages, and private repositories. GIGO (Gigo Installer for Go) tries to solve that problem, effectively being the golang equivalent of python's pip.
The direct result of using gigo, is that a requirements.txt file can now be used for golang projects, making it easy to componentize golang projects. Through using gigo, components can now have their own life cycles, and be managed, even within private repositories.
How Gigo Works
For all packages that can be fetched using the existing go get calls, Gigo acts as a wrapper. For elements in private repositories, gigo calls out to the appropriate revision control tool, like git.
Packages can be installed in several ways. You can use a go getable path, a go getable path and a commit number for versioned code, or the path, optional version, and a URL to pull the code from. If a url is used, gigo will copy the repository found at that url into the path specified.
Make sure you've set your GOPATH and then:
gigo install github.com/BurntSushi/toml gigo install github.com/BurntSushi/toml github.com/kr/fs gigo install -r requirements.txt gigo uninstall github.com/BurntSushi/toml gigo --help
First, make sure your GOPATH has been set. On unixes, simply run sh build.sh. On Windows, run build.bat.
Outputs are stored in dist/gigo and dist/gigo.exe respectively. At that point, you'll want to copy the binary produced, into a known location.
Requirements File Format
The gigo requirements.txt file follows python's pip as inspiration. Each line in the requirements file should represent a gigo fetchable item. In the case of private github repositories, you can specify a hash or tag, as well as a destination.
Hashes or tags can be specified following a hashmark. Similarly, a destination is specified by adding a comma. Below is an example of a valid requirements.txt file, using some random repositories.
github.com/BurntSushi/toml [email protected]:kr/fs#2788f0 [email protected]:liamstask/goose#8488cc4, bitbucket.org/liamstask/goose
Ideally, rcsget.go would be extended, to add support for mercurial, subversion, and pretty much anything else under the sun. We'd also like to make it easy to upgrade packages.
The MIT License (MIT)
Copyright (c) 2015 Lyrical Security Ltd
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
*Note that all licence references and agreements mentioned in the gigo README section above are relevant to that project's source code only.