Hi, Thanks for the suggestion. But what do we need to do for it?
Our RPMs bundle many libraries as you said but our RPMs use system packages including EPEL as much as possible. For example, our RPMs for AlmaLinux 9 bundle the following libraries: https://github.com/ursacomputing/crossbow/actions/runs/3354778483/jobs/5558561346#step:6:463 * Protocol Buffers * jemalloc * mimalloc * gRPC * Abseil * Google Could C++ * CRC32C * ORC Thanks, -- kou In <7730ef0d-d0f4-d2b8-210d-345b47161...@emailplus.org> "Using Arrow on RHEL/CentOS/Rocky and related linux distros" on Sun, 30 Oct 2022 16:34:51 +0300, Benson Muite <benson_mu...@emailplus.org> wrote: > Arrow releases are distributed as an RPM package for these > distributions. However, many dependencies are bundled with the > released RPMs, which may make using them in other software > problematic. Software collections[1] are similar to Python virtual > envs for RPM based distributions. They would enable unbundling > dependencies and make it easier to build on top of Arrow releases for > RHEL and related distributions. As an example Milvus uses Arrow, but > releases of Arrow used often lag behind the latest Arrow release[2]. > For those that use/build on top of RPM based distributions, would you > consider using/building on top of an Arrow software collection? > > 1) https://www.softwarecollections.org/en/ > 2) > https://github.com/milvus-io/milvus/blob/master/internal/core/thirdparty/arrow/CMakeLists.txt
