Should we provide a 'bootstrap' option?

As clean as the multicall binary is for installation, I find the process of actually setting everything up to work seamlessly a bit annoying, as I have to manually link to the binary several times with different names, or prepend every command with coreutils ....

I may be missing something, but as far as I have read the docs do not provide a quick and easy solution for this.

I propose adding an argument along the lines of coreutils --bootstrap that would automatically create links for every available function.

If not, what is the intended way to tackle this?

Either way, I am willing to implement the feature or update the docs to clarify this.

Start by reviewing the existing documentation for installing and using the multicall coreutils binary, then inspect the command entry point that handles its arguments. Clarify whether bootstrap should create links for every available function and what platform or installation constraints apply. Done means the intended setup is documented or the proposed option is specified with coverage for its expected behavior.