Good point! I'll add to that READMEs, LICENSEs, SBOMs (Software Bill of Materials), example configuration files, etc. How to supply all those files when all o

Good point! I'll add to that READMEs, LICENSEs, SBOMs (Software Bill of Materials), example configuration files, etc. How to supply all those files when all one gets is a single binary executable? Simple! Bundle everything in the executable. As a bonus, because the tool outputs these files, it can now generated them dynamically. For example instead of a bland configuration file, with all the possible integrations commented out, it could either try to auto-detect where it's running and what's available, or present the user with a question-answer session to fill in the details. ---- For example, a pet project of mine <https://github.com/volution/z-run https://github.com/volution/z-run>: z-run --readme # shows the README with `less` (if on TTY) or to `stdout` z-run --readme-html # for the HTML version to be opened in `lynx` z-run --manual # or --manual-man or --manual-html z-run --sbom # or --sbom-json or --sbom-html It even gives you the source code: z-run --sources-cpio | cpio -t ---- So, does your tool need a `.desktop` file? Just create a flag for that. Or, if there are too many such extra files needed to be placed wherever, just provide an `--extras-cpio` and dump them as an archive. Or if placing them requires some work, provide an `--extras-install`, but before `sudo`, kindly ask the user for permission. Granted all this requires some extra work, and increases the bulkiness of the executable, but: * all that extra code can be extracted into a common library; (I intend to do that for my software;) * if all these are compressed, especially being text-only, they are a fraction of the final executable; ---- I am especially proud of the `--sources-cpio` option. Is something broken with a particular version of the tool that you rely on? Great, instead of bumbling around GitHub to find the particular commit that was used to build this particular version, I can just get the sources from my tool and use those. All I need is the build tools, which in case of Go is another `.tar.gz`.