Add a way to bundle 3rd party Golang tools with your final executalbe

[ifireball]

We want to compile scripts that use popular Go-based tools like kubectl and jq. It would be great if we had a way to bundle them into our generated executable so they behave like shell builtins.

We can call this feature BYOB - Bring Your Own Builtin 😄

[yassinebenaid]

Good idea 👍 . We will add this feature for sure. Go can already link C programs. I was thinking to allow linking with C as well .

[xplshn]

I don't think it is a good idea, bunster could instead provide an easy way to embed statically linked binaries.

I mean, embed already exists, but something that lets you obtain binaries from places like ppkg or dbin (yes, I know, I develop dbin, but it has 4 thousand (more coming soon btw) statically linked programs in its repos, including jq, yq, all of those popular cli tools a script may need)

---

Statically linked programs run in all systems that are of the same architecture and OS.

[yassinebenaid]

as you said, we already have embed. so anyone can embed the binary. and use it at runtime. But my idea is a little different.

if we think about it. we support modules already. so when you require a bunster module. bunster's package manager will fetch that module to your machine. and every time you build your binary. bunster will compile those external modules to golang. then merges them with your module and then builds the binary.

So why not allow people to use Golang to write modules. and then bunster will skip the steps to convert the script to golang. it will merge them directly to your module.

not only that, but those external go modules can also require other dependencies as well.

for example, I can require kubctl to my module and have it compiled with my binary. now I have a fully static binary that has kubctl available all the ime. no binding, no $PATH search. and even the user experience is pretty straightforward.