As recommended by the rdkit conda package maintainer, we now require only librdkit-dev as a host requirement and enforce a runtime pin on rdkit via the version of librdkit-dev. However, it turns out that only the rdkit package depends on boost, so we can build against a version of libboost that is incompatible with the run time pin. For example, librdkit-dev-2025.4.3 might be resolved in the host requirements and we also resolve libboost-1.8.2. The runtime pin for rdkit is then 2025.4.3 to 2025.4.4, but this requires libboost-1.8.6. As such, we need to add rdkit to the host requirements too.
As recommended by the
rdkitconda package maintainer, we now require onlylibrdkit-devas a host requirement and enforce a runtime pin onrdkitvia the version oflibrdkit-dev. However, it turns out that only therdkitpackage depends onboost, so we can build against a version oflibboostthat is incompatible with the run time pin. For example,librdkit-dev-2025.4.3might be resolved in the host requirements and we also resolvelibboost-1.8.2. The runtime pin forrdkitis then2025.4.3to2025.4.4, but this requireslibboost-1.8.6. As such, we need to addrdkitto the host requirements too.