So worth to extend this chain to: "./configure && make all check dist && tar -x apache-couchdb-2.0-some-hash.tar.gz && cd apache-couchdb-2.0-some-hash && ./configure && make all check" - not real command, but with fixing tar and cd part it will be close to.
Wouldn't it be enough then to only `make dist` in the git repo (without make all check) and leave the `make all check` part for the second make run, when running in the directory where we extracted the tarball? Otherwise we are duplicating the work of the all & check targets. Since we will be running on builds.a.o we should try to minimize build times when possible, I think.
If it's possible to test "make install" on CI into some fake root - that would be also helpful.
make install should be possible whenever we run the build in a Docker container (so, for all Linux flavors). We'll have to see for other OSes. How would you verify that the make install was successful?
Kind regards Bastian
