fixed centos build and updated readme on master

Author: tdudgeon

Dockerfile-build-centos

@@ -8,9 +8,9 @@ LABEL maintainer="Tim Dudgeon<[email protected]>"
 
 # centos8 now comes with a version of boost that is compatible with RDKit (unlike centos7).
 
-RUN sed -i 's/enabled=0/enabled=1/' /etc/yum.repos.d/CentOS-PowerTools.repo &&\
-  yum -y install epel-release &&\
-  yum update -y &&\
+# Note: doing a yum update' renames the CentOS-PowerTools repo to CentOS-Linux-PowerTools
+RUN yum -y update &&\
+  sed -i 's/enabled=0/enabled=1/' /etc/yum.repos.d/CentOS-Linux-PowerTools.repo &&\
   yum install -y --setopt=tsflags=nodocs --setopt=override_install_langs=en_US.utf8\
   tk-devel\
   readline-devel\
@@ -21,18 +21,13 @@ RUN sed -i 's/enabled=0/enabled=1/' /etc/yum.repos.d/CentOS-PowerTools.repo &&\
   cmake3\
   python3-devel\
   python3-numpy\
-  boost\
   boost-devel\
-  boost-python3\
   boost-python3-devel\
   eigen3-devel\
   swig\
   git\
   wget\
   java-11-openjdk-devel\
-  #postgresql-server\
-  #postgresql-server-devel\
-  #postgresql-plpython3\ 
   zip\
   unzip\
   freetype-devel &&\

Dockerfile-java-centos

@@ -5,6 +5,7 @@ FROM centos:8
 LABEL maintainer="Tim Dudgeon<[email protected]>"
 
 RUN yum update -y &&\
+  sed -i 's/enabled=0/enabled=1/' /etc/yum.repos.d/CentOS-Linux-PowerTools.repo &&\
   yum install -y --setopt=tsflags=nodocs --setopt=override_install_langs=en_US.utf8\
   java-11-openjdk-headless\
   boost\

Dockerfile-python3-centos

@@ -5,9 +5,8 @@
 FROM centos:8
 LABEL maintainer="Tim Dudgeon<[email protected]>"
 
-RUN sed -i 's/enabled=0/enabled=1/' /etc/yum.repos.d/CentOS-PowerTools.repo &&\
- yum -y install epel-release &&\
- yum update -y &&\
+RUN yum update -y &&\
+ sed -i 's/enabled=0/enabled=1/' /etc/yum.repos.d/CentOS-Linux-PowerTools.repo &&\
  yum install -y --setopt=tsflags=nodocs --setopt=override_install_langs=en_US.utf8\
  python3\
  python3-devel\

README.md

@@ -46,10 +46,14 @@ For each RDKit version (image tag) we build a number of images:
 * `Release_2020_03_1` - build from RDKit Release_2020_03_1 release tag. These images should never change [1]. Images have tag of `Release_2020_03_1`
 * `Release_2020_03_2` - build from RDKit Release_2020_03_2 release tag. These images should never change [1]. Images have tag of `Release_2020_03_2`
 * `Release_2020_03_3` - build from RDKit Release_2020_03_3 release tag. These images should never change [1]. Images have tag of `Release_2020_03_3`
+* `Release_2020_03_4` - build from RDKit Release_2020_03_4 release tag. These images should never change [1]. Images have tag of `Release_2020_03_4`
+* `Release_2020_03_5` - build from RDKit Release_2020_03_5 release tag. These images should never change [1]. Images have tag of `Release_2020_03_5`
+* `Release_2020_03_6` - build from RDKit Release_2020_03_6 release tag. These images should never change [1]. Images have tag of `Release_2020_03_6`
 * `Release_2020_09` - build from RDKit Release_2020_09 branch and occasionally rebuilt as the code gets updated. Images have tag of `Release_2020_09` 
 * `Release_2020_09_1` - build from RDKit Release_2020_09_1 release tag. These images should never change [1]. Images have tag of `Release_2020_09_1`
 * `Release_2020_09_2` - build from RDKit Release_2020_09_2 release tag. These images should never change [1]. Images have tag of `Release_2020_09_2`
 * `Release_2020_09_3` - build from RDKit Release_2020_09_3 release tag. These images should never change [1]. Images have tag of `Release_2020_09_3`
+* `Release_2020_09_4` - build from RDKit Release_2020_09_4 release tag. These images should never change [1]. Images have tag of `Release_2020_09_4`
 
 
 [1] Where we say that the images should never change what we really mean in that the RDKit content should never change. We may rebuild these images occasionally when we find further improvements, and the underlying Centos/Debian packages may be updated, but the RDKit code should be exactly the same.