How do you handle install-time dependencies? #5299
Unanswered
scowalt
asked this question in
Help and Questions
Replies: 1 comment 1 reply
-
here's what I would do:
In this case: I have not tested, but should work:
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I want to create a package for gomerge.
This is a command line utility built in golang that contains no Windows binaries. I wanted to do what homebrew would do, which is build the binary from source, then put the binary into the user's PATH.
Building
gomerge
would depend on thego
package at install-time. However, the current docs are a bit unclear as to how to include an install-time dependency:I highly doubt that scoop will know to install golang based on my downloading of a
.7z
file of the source code.For now, I will add a pre-install script that does
scoop install go
. However, this feels a bit hacky. For example,go
will stay on the user's system if/when they uninstallgomerge
, which feels like an unintended side effect. Maybe this is what homebrew does?Beta Was this translation helpful? Give feedback.
All reactions