Use arrow-cpp's run_export

jakirkham commented 4 years ago

Makes sure we use arrow-cpp's run_export to determine the version of arrow-cpp we use at runtime.

Checklist

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

conda-forge-linter commented 4 years 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) and found it was in an excellent condition.

jakirkham commented 4 years ago

By default, with the pin_compatible('package_name') function, conda-build pins to your current version and less than the next major version.

So this would be a much looser pin than we have in run_exports currently as it would allow anything up to (but excluding) arrow-cpp 2.

xhochy commented 4 years ago

😱that was then not so good. Glad this is fixed now.

jakirkham commented 4 years ago

No worries. We are handling it quickly and the number of packages affected is small. 🙂

conda-forge / pyarrow-feedstock