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.
