nealrichardson commented on PR #42210: URL: https://github.com/apache/arrow/pull/42210#issuecomment-2180582378
> > I also wonder whether GCS is worth including. > > I agree + though similar when I checked if S3 alone was sufficient for quieting the message. I'm happy to pull GCS out of this, though IMO we should also add GCS to [the block list](https://github.com/apache/arrow/blob/89d6354068c11a66fcec2f34d0414daca327e2e0/r/R/arrow-info.R#L143) so that it's not being checked if we do that too. > > I'm happy to do this in this PR if we want. Right, we would want to change that message. On the one hand, users won't generally experience this because they'll get a binary from CRAN. On the other, GCS increases build time there and increases the BDR attack surface. I don't know how big that risk is and if demand for GCS outweighs it--I haven't noticed demand for GCS, but maybe I'm not looking in the right places. I guess we could leave it on, and if we get dinged on CRAN, we know how to turn it back off? -- 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]
