Use stricter run_exports

[traversaro]

See RoboStack/ros-humble#6 (comment) for a discussion on why the run_exports should be stricter.

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

[conda-forge-linter]

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) and found it was in an excellent condition.

[traversaro]

fyi @danzimmerman

[traversaro]

@conda-forge-admin, please rerender

[traversaro]

Once we merge this, we also need to prepare a repodata patch similar to conda-forge/conda-forge-repodata-patches-feedstock#286 .

[Tobias-Fischer]

Thanks @traversaro!

[Tobias-Fischer]

Are you happy to write the repodata patch as well, @traversaro?

[traversaro]

Are you happy to write the repodata patch as well, @traversaro?

Sure! (Self-remainder of how to compute the timestamp: https://github.com/conda/conda-build/blob/84818bc3bbe26f112dfa177f1a49057221599f74/conda_build/metadata.py#L1428)