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 collections, right? It seems that software collections don't provide them: https://www.softwarecollections.org/en/scls/?search=abseil https://www.softwarecollections.org/en/scls/?search=grpc (Note that our RPMs already use system Thrift package.) So it seems that software collections doesn't help us... 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 <benson_mu...@emailplus.org> wrote: > 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 >> * jemalloc >> * mimalloc >> * gRPC >> * Abseil >> * Google Could C++ >> * CRC32C >> * ORC > 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 > jemalloc is available in this ecosystem, but is not enabled in this > build. > > Using a software collection would enable much easier build deployment > and customization. In particular some of these packages follow a live > at head philosophy and others do not, so what is packaged by the > distribution may not have features used in Arrow. A software > collection would enable easy packaging of a tested combination. It > would also enable easy modification of selected components improving > developer productivity since it would setup the development > environment correctly and this would closely match the production > environment. >
