Am 11.08.2022 um 00:44 schrieb Terence Kelly:
I call this feature "literate executables" in homage to Knuth's "literate programming": binaries such as executables and libraries (.so) compiled from C/C++ can emit their own source code on demand.
Where do you draw the line between "source code", "patches applied after extracting the archive", "tool used to build the program", "operating system below the toolchain"? So what should be included in the executable and what should be left out? How does your approach compare to https://reproducible-builds.org/, which records similar information but stores it outside the resulting binary? Roland
