On 11/2/22 10:32, Sutou Kouhei wrote:
Hi,
As an example Arrow is packaged in Fedora/EPEL. The spec file does not
bundle Abseil, thrift, gRPC,
https://src.fedoraproject.org/rpms/libarrow/blob/rawhide/f/libarrow.spec
Because Fedora ships recent Abseil, Thrift and gRPC. It
doesn't use software c
..
Thanks,
--
kou
In <8012d57d-6abb-fabd-dbd1-ea630c6c6...@emailplus.org>
"Re: Using Arrow on RHEL/CentOS/Rocky and related linux distros" on Tue, 1
Nov 2022 09:54:37 +0300,
Benson Muite wrote:
> On 10/31/22 00:14, Sutou Kouhei wrote:
>> Hi,
>> Thanks for the sugge
On 10/31/22 00:14, Sutou Kouhei wrote:
Hi,
Thanks for the suggestion. But what do we need to do for it?
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
* jemal
/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,
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