Greg Landrum

@markussitzmann : It also didn't work for me when I tried to force boost 1.65.1. The current branch is set to use 1.65, which grabs 1.65.1 by default. I'm using...

Unless you need it for something else, you can probably skip the boost build now (line 51 in your Dockerfile); that will use the boost build recipe from the RDKit...

FWIW: these two containers are what I am using to do conda RDKit builds: https://github.com/rdkit/rdkit_containers/tree/centos6_cleanup/docker/centos6_modern_bare https://github.com/rdkit/rdkit_containers/tree/centos6_cleanup/docker/centos6_modernconda

Yeah, assuming that there is an anaconda distrib that supports it by then, I will do Python 3.7 builds (and probably retire 3.5) for the 2018.09 release.

@sriniker : if you have time and inclination to look at this, I'd lover your comments. I have a bit more work to do before marking it as "done", but...

I can do the centos6 test; I have a VM that I use for my conda testing. I'll give that a try this evening.

I wonder about VS2008? (Or maybe we should explore moving to something "a bit" more up-to-date for py27 on windows)

I updated the recipe for boost and the rdkit to use boost=1.62 and the rdkit release branch (just to ensure up-to-date production code for the testing phase) and it builds...

the other thing that is worth considering, and that I'm trying now as well, would be to use the normal conda version of boost: 1.61. This would spare us from...

But 1.61 would just cause problems for people who want to build their own version of the RDKit using the conda recipes, right? That's not a huge concern to me.