Stripping the release tarballs #5618
I think we should be a bit more aggressive as to what we bundle in the release tarballs. I see it similar to how autotools handles
Finally, @bnoordhuis suggested we bake an alternate readme that we push as part of the release packages that more accurately represents whats included and how to use it.
Thoughts? Anything else that should go?
Instead of an alternate
It seems to me that the build instructions dominate the
CLARIFICATION: So instead of stripping build stuff out of an alternate README, strip it out of the canonical README and have the build instructions live in its own document. So we still only have one README and one place where build instructions live.