I
I
Igor Arkhipov2021-09-16 20:00:08
go
Igor Arkhipov, 2021-09-16 20:00:08

Is there an alternative package manager for Go binaries?

Is there a package manager and/or easy way to install and update Go utilities without installing Golang itself on a macOS machine?

For example, the conditional assetfinder is set only in this way go get -u github.com/tomnomnom/assetfinder(well, or manually, of course). A slightly more popular gron is in Homebrew brew install gron. In the first case, Golang is required in its entirety, which, as it were, is not needed, and it is not clear what is happening with the updates. In the second case, I get a working binary that will be updated seamlessly and the utility is already being used in Villarribo, while the correct GOROOT and GOPATH variables are set in Villabaggio.

I found only bingo "The missing package manager for golang binaries (its homebrew for "go install")", but it ironically requires Golang.

Answer the question

In order to leave comments, you need to log in

3 answer(s)
I
Igor Arkhipov, 2022-03-15
@IgorArkhipov

There is a tool to update globally installed Go binaries
https://github.com/Gelio/go-global-update

U
uvelichitel, 2021-09-17
@uvelichitel

As far as I know, there is no generally accepted package manager. But Go was designed in such a way that the application was compiled into one binary, without a shared library and dependencies. To install an application, you simply place the binary on the $PATH executable path, to demolish the application, you delete the binary. Developers of serious applications compile release binaries for major platforms. For the notorious, conditional assetfinder, here is the current release binaries page https://github.com/tomnomnom/assetfinder/releases/... There is darwin-amd64.

A
Alexandre, 2021-09-22
@Alexandre

in our office, this is done like this (I would call it through F):
1) the binary is assembled in the docker.
2) the binary is rolled out of the docker into production
3) the docker is destroyed in
total:
the binary without dependencies in production
is a necessary condition: the docker image must correspond to the production environment, you cannot build the binary in alpina but roll it out to centos or debian.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question