-
Notifications
You must be signed in to change notification settings - Fork 21
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
Compiled custom binary export #58
Comments
Love the idea, but I'm not sure that there's a good way to do what you're describing. Anything that bakes metadata into the executable itself (like with packr) means re-building from source. That's almost certainly going to be tougher from an environment setup perspective than a shell alias—I don't think tusk could expose binary building from CLI without bringing the entire I'd also argue that sharing a I'm happy to leave the issue open in case we can figure out a clean way to do this, but my intuition is that a shell alias is probably as easy as it's possible to be. |
Is your feature request related to a problem? Please describe.
I'm really interested about your CLI metadata feature, giving me the possibility to create a good QoL boosted cli tool with ease, and thanks for that! 👍
But the current solution has some lack in my opinion:
tusk.yml
configuration file. The user will have to get the configuration file manually or via a custom script. It's kind of a TOIL thing.Describe the solution you'd like
I would like the possibility to "compile" a dependencies/configuration free binary to be ready to use "out of the box" without having to deal with the go language.
Something like that:
Would not it be awesome?! 😄
Additional context
I'm currently not a Go expert, but I might thing this is gonna help : https://github.com/gobuffalo/packr/tree/master/v2
If you think this as no place to take on
tusk
, a cook book may be written instead.Regards
The text was updated successfully, but these errors were encountered: