srh/rethinkdb-package-builder

rethinkdb-package-builder's Issues

arch support ?

Hello Sam,

It's possible to support/add arm64 arch?

Have some way to specify ALLOW_WARNINGS=0 in builds

Right now, all builds with --builds use a build/Dockerfile. It might be handy to have some way to specify ALLOW_WARNINGS=0 when testing out a new platform (which passes -Werror to the compiler), so that we can use rethinkdb-package-builder to confirm the latest version of RethinkDB builds without warnings on any given new OS version.

Maybe a new option, --werror-builds, that uses a new werror_builds/Dockerfile, is the way to go.

centos8 system setup is broken: Failed to download metadata for repo 'appstream'

Step 3/7 : RUN yum install -y openssl-devel libcurl-devel wget tar m4     git-core gcc-c++ which make python2 boost-devel     bzip2 patch clang     perl rubygems ruby-devel rpm-build
 ---> Running in 936adb675d6c
CentOS Linux 8 - AppStream                       36  B/s |  38  B     00:01    
Error: Failed to download metadata for repo 'appstream': Cannot prepare internal mirrorlist: No URLs in mirrorlist
The command '/bin/sh -c yum install -y openssl-devel libcurl-devel wget tar m4     git-core gcc-c++ which make python2 boost-devel     bzip2 patch clang     perl rubygems ruby-devel rpm-build' returned a non-zero code: 1

Support for s390x

Some ubuntu docker images already have an s390x tag, but for those that have no s390x tags, the https://hub.docker.com/r/s390x/ubuntu contains docker images.

So: using the https://hub.docker.com/r/s390x/ubuntu images for s390x builds over the regular ubuntu images would allow having s390x build.

---

Sorry, too much s390x. Also, it is not a priority thing either. All build steps are the same, even the packages, only the base image should be "replaced" in the Dockerfiles.