On 24 September 2025 at 16:49, Steffen Möller wrote: | just to keep you all in the loop. An r-cran-arrow package is produced by the current packaging effort of apache-arrow. You are all fine with that, right? | | Once I get some positive vibes about it, I would want to upload to experimental if not unstable. Bz2 and zstd I would want to see, still. Other blockers? | | Best, | Steffen | | > arrow_info() | | acero TRUE | dataset TRUE | substrait FALSE | parquet TRUE | json TRUE | s3 FALSE | gcs FALSE
These two cloud libraries are very useful in many contexts but hard to package due to the SDKs needed. I am totally fine with skipping these. | utf8proc TRUE | re2 TRUE | snappy TRUE | gzip TRUE | brotli FALSE | zstd FALSE These two compressors should be easy to add as we have the lib*-dev packages. | lz4 TRUE | lz4_frame TRUE | lzo FALSE | bz2 FALSE These two compressors should be easy to add as we have the lib*-dev packages. | jemalloc FALSE This one should be easy (libjemalloc-dev) but I am not sure I care :) | mimalloc TRUE | | Memory: | | Allocator mimalloc | Current 0 bytes | Max 0 bytes | | Runtime: | | SIMD Level sse4_2 | Detected SIMD Level sse4_2 My locally built arrow has a better optimisation but such is life. This choice seems fine. | Build: | | C++ Library Version 21.0.0 | C++ Compiler GNU | C++ Compiler Version 15.2.0 | Git ID 72b7209c8cd25dc974accdc65c1bd9c7dcc2d7a Thanks for your persistence in packaging this. Cheers, Dirk -- dirk.eddelbuettel.com | @eddelbuettel | [email protected]
