[BUG] librdkit-dev doesn't enforce boost constraint

[lohedges]

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.

[lohedges]

Gah, it looks like this doesn't work. Adding both to the requirements gives (for Linux Python 3.11):

    rdkit:                            2024.03.5-py311hafb272b_0              conda-forge         
    librdkit:                         2024.03.6-h04b5189_0                   conda-forge         
    librdkit-dev:                     2024.03.6-ha4b6fd6_0                   conda-forge  

So, if we pin based on rdkit, it would be incompatible with librdkit. I'd need to check whether this actually causes problems.

[lohedges]

Just to note, the initial issue isn't a problem when you leave rdkit unpinned, since a correct version is resolved, but it is when you pin.

[lohedges]

It looks like this is mostly due to the change in the naming structure for the Boost conda packages. We currently depend on boost, but this should now be libboost-devel and libboost-python-devel, which allow for matching with newer RDKit packages.