Move building of python arrow modules from pyarrow to apache-arrow. #30285
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A couple things here:
need zstd-static because:
CMake Error at /usr/lib64/cmake/zstd/zstdTargets.cmake:107 (message):
The imported target "zstd::libzstd_static" references the file
"/usr/lib/libzstd.a" uses=cmake/configure
but this file does not exist. Possible reasons include:
cherry-pick a patch (from 2016) to rapidjson that allows a user of it
(apache-arrow) to build with gcc-14.
Add environment variables to build so the python build modules
have access. I had hoped to localize these or use substitution
in the environment block, but that is not supported.
A nested pipeline's environment does not pass through to a
uses
step. chainguard-dev/melange#1548RFE: support substitution in environment.environment in nested pipelines or actions chainguard-dev/melange#1402
drop unnecessary runtime dependency from libarrow to libarrow.
remove pyarrow.
bump the epoch on apache-arrow to 3 to be newer than pyarrow was.
provide multiple versions of the python modules, and make them provide 'pyarrow' for backwards compat.