paleolimbot opened a new issue, #35049: URL: https://github.com/apache/arrow/issues/35049
### Describe the enhancement requested There are a few things that I've noticed over the last few months of working with/installing Arrow and the R package on various platforms. I think some of these may have come up in previous tickets and as I go through actually trying some of these I will attempt to locate them. The main idea is that when a contributor does a git clone of Arrow and opens up the package in RStudio or VScode, the static nightly builds of Arrow built for the R package should be sufficient for a user to run `devtools:test()`. When I was debugging the "files are kept open too long on Windows" problem I used that strategy to avoid setting up a Windows Arrow build and it worked great! (Maybe this is even documented already...if it is, moving that documentation to a more prominent place may be helpful). Another common thing I've run up against is that the configure script enables `pkg-config` by default. The build of Arrow resolved by pkg-config is almost never the right one...it's usually too old or has the wrong features enabled. At the very least we need to check the version of whatever gets resolved by pkg-config and maybe we should consider disabling it by default. This is a particular issue with homebrew. ### Component(s) R -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
