Add run export to metapackage too

conda-forge / coin-or-cbc-feedstock

A conda-smithy repository for coin-or-cbc.

BSD 3-Clause "New" or "Revised" License

3 stars 11 forks source link

Add run export to metapackage too #26

Closed conda-forge-admin closed 2 months ago

conda-forge-admin commented 2 months ago

Hi! This is the friendly automated conda-forge-webservice.

I've started rerendering the recipe as instructed in #25.

If I find any needed changes to the recipe, I'll push them to this PR shortly. Thank you for waiting!

Here's a checklist to do before merging.

[ ] Bump the build number if needed

conda-forge-webservices[bot] commented 2 months ago

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

hmaarrfk commented 2 months ago

A few packages like lemon https://github.com/conda-forge/lemon-feedstock/pull/39

depend on coincbc and thus don't receive the run export.

This should address things.

Let me know if you have any questions

tkralphs commented 2 months ago

I have to admit that my conda knowledge is not quite at the level to fully understand this, but from my brief reading just now, I think it makes sense. @wolfv would certainly be a better person to say for sure, but I will merge if he doesn't say otherwise.

wolfv commented 2 months ago

Thanks for merging @tkralphs - the idea of run exports is that packages compiled against a specific version of coin-or-cbc would automatically get constraints applied towards the compatible version range.

For example, if I now compile a package against coin-or-cbc, I would be limited to >=2.10.2,<2.11.