amoeba commented on issue #46646:
URL: https://github.com/apache/arrow/issues/46646#issuecomment-3063443524

   I understand @WillAyd's perspective here. It'd be nice if all checks were 
entirely self-bootstrapped.
   
   Imagine I'm a contributer who wants to contribute a PyArrow documentation 
change and I want to use pre-commit to make sure my change is well-formatted. I 
do this,
   
   1. Check out arrow and cd into the checkout
   2. Install pre-commit (like with apt or brew)
   3. Run `pre-commit install`
   4. Edit the .py file I want
   5. git add and commit the file
   
   At this point, I'll run into the errors @WillAyd reported (no Rscript, no 
ruby, no ruby dev headers). This is a bit of a disincentive for contributors to 
use pre-commit. 
   
   The R situation can be fully or partially resolved by [migrating to 
Air](https://github.com/apache/arrow/issues/46592) but I'm not sure about the 
Ruby bit.
   
   Is the best we can do right now just to document this?


-- 
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: github-unsubscr...@arrow.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to