-
-
Notifications
You must be signed in to change notification settings - Fork 7.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hugo binary seems to have external dependency, despite README.md's claim #10136
Comments
Thanks, I have removed that sentence. Some (optional) parts of Hugo does depend on certain binaries being available in the PATH (e.g. I suggest you take further questions at https://discourse.gohugo.io/ |
Hi @flyn-org, Interesting discussion! I should add a weak-dependency on Go in the Debian package too. Besides the existing
in the next package upload for Debian. Go is indeed rather large, so I think it is best we merely suggests to the end user to install Go manually. Thanks for the neat idea! |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Hugo's README.md states "The Hugo binaries have no external dependencies." However, running
hugo server
causes the errorError: failed to download modules: binary with name "go" not found
. This is fixed by installing the Go tools. So, it seems Hugo has taken on some external dependencies.I am the maintainer of the Fedora Hugo package. Changing the Hugo package to depend on golang-bin brought in a large volume of dependencies, such as GCC. This is not optimal for some uses, such as CI pipelines, which benefit from small installs. We are trying to come up with a solution for this, but I thought I would investigate where this dependency came from.
What version of Hugo are you using (
hugo version
)?Does this issue reproduce with the latest release?
Yes.
The text was updated successfully, but these errors were encountered: