remove the now obsolete rdkit-postgresql95 recipe #68
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
greglandrum
added a commit
that referenced
this pull request
Jun 8, 2018
* updated patch file * fix issue #27 * comply with the formatting applied by #1078 * use cmake to build the postgresql cartridge * update the release tag * update release label * COPY the recipes instead of cloning the git repo * update main build to 2016.9.4 * update rdkit version * get boost builds working with py36 * rdkit build for windows and py36 * linux and mac update * psql update * make pandas and pillow dependencies explicit * bump release * - enable rdkit, rdkit-postgresql95 and rdkit-postgresql conda builds on all platforms * - added missing bld.bat files * - added recipes for Windows PostgreSQL recipes * - added patch to build postgresql <=9.5.2 with VS2015 * switch which version is being built * Update which code is built * Update which code is built * add cheto build * switch to master and the rdkit repo * update which boost libraries are built * update boost dependency to 1.61 for unix * switch cheto to no-arch * switch to allowing versions of numpy greater than 1.11 instead of requiring a particular version * add a docker setup to do linux builds of the RDKit code * this works on the mac, but needs more testing * works on linux, and the mac * switch back to Release branch * remove runtime conda deps * remove python 3.4 support * update rdkit-postgresql95 build * Updates conda version to conda 3.0 compatible version * builds on the mac * stop requiring a particular conda version stop building the c++ tests * add freesasa to linux/mac builds * switch to requiring numpy 1.12 at build and >= 1.12 at runtime * update * try restricting this to psql9.5 * get postgresql95 build updated and working remove python dependency switch to 9.5.10 * get rdkit-postgresql95 build updated and working * switch boost download location for unix * oops * backup * another unsuccessful attempt at a mac build * legacy cmake argument removed * start using conda-build 3 syntax * update cairo * update to reflect new layout * Switch to the production branch. * remove un-necessary dependencies * rename cairo_nox back to cairo, update the rdkit meta.yaml to reflect that * do not activate the root environment... <sigh> * remove 'source activate root' from cairo_nox recipe * update the rdkit-postgresql recipe for release 2018.03 (#65) * initial round of updates targeting rdkit 2018.03.1 * build multiple variants of the cartridge for different versions of postgres * build the cartridge using static linking * remove the obsolete patch files * speed up build (#67) * remove the now obsolete rdkit-postgresql95 recipe (#68) Yeah, this one’s easy. Thanks! * try to force cairo_nox on linux builds * force a pandas version on build * allow pandas <=0.22 * windows builds should not be so huge
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
this one is a bit trivial, but it shouldn't trigger any big concerns I think.