Скачать или смотреть Handling Go Modules with Packages that Require make install

Discover how to manage Go packages that require `make install` within Go Modules without resorting back to GOPATH.
---
This video is based on the question https://stackoverflow.com/q/65058016/ asked by the user 'susdu' ( https://stackoverflow.com/u/5543739/ ) and on the answer https://stackoverflow.com/a/65058551/ provided by the user 'Volker' ( https://stackoverflow.com/u/1266756/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Using Go Modules with packages that require "make install"

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Handling Go Modules with Packages that Require make install

Using Go Modules has revolutionized the way Go developers manage dependencies. However, some packages may come with certain requirements that complicate their integration into a module-based workflow. One common scenario that developers face is working with external packages that necessitate running a make install command after the package is fetched. In this post, we will explore how to deal with this issue effectively and whether reverting back to GOPATH is necessary.

The Challenge: What Happens to Packages Requiring make install?

When you utilize the command go get, Go fetches the desired package, but if the package's installation process requires running make install, things can become tricky. The following is a breakdown of the challenge:

After fetching the package using go get, you may need to navigate to the $GOPATH/src directory.

In the folder of the fetched package, running make install performs necessary setup tasks defined by the makefile.

With Go modules, executing go mod vendor creates a copy of the package in the vendor directory; however, this copy is no longer a Git repository, which is often essential for running make install successfully.

This raises an essential question: Does this mean that the package cannot be used in a module?

The Answer: Reverting Back to GOPATH or Contacting the Author?

The short answer to this query is Yes, you potentially cannot use that package directly within Go Modules. Here’s what you can do next:

1. Contact the Package Author

If you rely on a specific tool or library, consider reaching out to the author of the package:

Ask them to review their makefile and consider transitioning to a more module-friendly installation process.

A dialogue with the package maintainer can lead to updates that improve compatibility with Go Modules.

2. Consider Reverting to GOPATH

If immediate usage of the package is critical and you can’t wait for a solution, reverting back to using the traditional GOPATH approach may be necessary. Here’s how to do that:

Set Up GOPATH: Make sure your GOPATH is correctly set up in your environment.

Use go get: Fetch the desired package directly into your $GOPATH/src directory.

Run make install: Navigate to the package directory and run make install as usual.

While this workaround may allow for continuing your work, it’s essential to recognize the downsides of leaning back into a more antiquated method of dependency management in Go.

Conclusion

While the transition to Go Modules has enhanced dependency management, challenges remain, especially when handling packages requiring specific installation commands like make install. If you find yourself stuck, remember that reaching out to the package's author for improvements can help cultivate a better ecosystem for all developers. Alternatively, reverting back to GOPATH is an option but should be considered a temporary measure.

By addressing these challenges head-on and advocating for updates from package maintainers, the community can encourage better practices and smoother integrations for everyone involved.