But, maybe a better solution is to faithfully record the current git (or other VCS) details you'd need to find the code which resulted in the binary? That way you have access to the source in its natural state.
On Thursday, October 19, 2017 at 11:49:39 AM UTC-7, Alex Buchanan wrote: > > We use go-bindata to bundle text files (html, js, css, yaml) into our > binary. I bet you could use it to bundle Go source. > > https://github.com/jteeuwen/go-bindata > > -Alex > > On Thursday, October 19, 2017 at 9:46:37 AM UTC-7, Samuel Lampa wrote: >> >> Hi Gophers, >> >> *Question:* Is there any way to include a readable verison of the source >> code of my program into the compiled Go binary, either in plain text, or >> the ability extract it somehow, with some go tooling or 3rd party tools? >> >> *Background:* The reason for asking is that we are using Go to write >> scientific workflows with scipipe <http://scipipe.org>. This means we >> can compile our scientific workflows into static binaries for easier >> deployment and protecting against undocumented code changes that code make >> us loose track of the provenance ("complete track record") of the steps ... >> and potentially lead to flawed science ("shudder"). >> >> But with compiled binaries, we instead run into another problem of >> provenance: Allowing ourselves and others to inspect that a particular >> workflow binary actually does what it says. >> >> Thus, having a statically compiled binary with the source code included >> in some form, would be the best of two worlds. >> >> Cheers >> // Samuel >> PhD Student @ pharmb.io >> > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
