nealrichardson commented on issue #35049: URL: https://github.com/apache/arrow/issues/35049#issuecomment-1526001683
Another thought I had while 🚶 🐕 : we could detect that we're in a git checkout, and if so, instead of doing autobrew, do the bundled build. And when the bundled build happens in a git checkout, we could make it build into a (gitignored) directory inside the project. Then we would add that location to our places to look for arrow already on the system, which we'd use, assuming it passes the version check. So the first time, it would build, and the next time you installed the R package, it would pick up the C++ build and not have to redo it. The downside to going farther down this direction is that we will need better tooling or at least instructions for what to do when *this* build gets out of sync, but even if the instruction is `rm -rf`, it would solve the problem of iterating on a single branch at one time. For anyone who is a repeat contributor who would run into the sync issues, we should probably be nudging them towards maintaining a proper C++ build anyway, so this is for the one-time fix use case. -- 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]
