nealrichardson commented on issue #35472: URL: https://github.com/apache/arrow/issues/35472#issuecomment-1542265545
> @paleolimbot while on-the-fly vendoring can be useful for some, it deviates the CI even further from the build process used for (CRAN) releases, which relies on 3rd parties (me) providing libarrow builds for win/mac that the R package can download. We vendor the C++ source before submitting to CRAN, so the .tar.gz source package one installs there has it included. What @paleolimbot was mentioning would make that pre-build step we do become a part of the remotes/devtools workflow, so it would be more like the CRAN scenario. > > I think the priority should be to make the arrow CI self sustaining and focus on getting such libarrow nightlies and releases built and published for the platforms that you want to support. For windows, we already build and host the static libraries for releases (e.g. https://apache.jfrog.io/ui/native/arrow/r/12.0.0/libarrow/bin/windows/), so we may be able to just drop the rwinlib path if that's helpful. Mac is more involved with the autobrew/bottle setup, but I'm sure we could find ways to make that more self-sustaining. -- 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]
