Hi folks,
> I fixed one more issue that prevented us from building CouchDB from
within a release tarball
this line from Jan in the release testing thread reminded me of another
question I pondered for the CI topic.
Right now we clone/update the repo from git and then run "./configure &&
make all check dist" and that's it. I wonder if that is enough?
Currently I am not doing anything with the binary or the tarball that is
produced in this step.
My guess would be that the one following would yield a more valuable
feedback:
* Start CouchDB via the binary that has been produced by make all and at
least run some simple smoke tests against that instance -- or is
something like that done during make all/make check?
* Or, run make dist first to only produce a tarball, then use that
tarball to actually build the CouchDB binary - instead of building
directly from the git checkout. (This would catch the kind of issues
mentioned by Jan above, I suppose).
* Some combination of the above, for example, build the binary from a
dist tarball, start it, run smoke tests.
What do you think?
Disclaimer: I didn't take the time yet to really check the Makefile (and
also my make skills are close to non-existing), so if the Makefile
already covers parts of this, my bad.
Kind regards, merry Christmas & happy holidays
Bastian
