mgorny commented on PR #45854: URL: https://github.com/apache/arrow/pull/45854#issuecomment-2805643046
> > I wonder if this change could make resolving #45576 easier > > I started down this path and ended up removing it in [9f5df6e](https://github.com/apache/arrow/commit/9f5df6e94a8eddcba82115f631935d40e15bd57e) after some feedback and to keep the scope of this more refined. However, I don't think it would be that difficult to achieve with meson-python; generally the way meson forces you to handle dependencies as subprojects helps to streamline your build configuration Yeah, I can imagine people not wanting to have to maintain translation from Meson to CMake (much like my earlier PR #45580 was rejected). However, I think this will become simpler if it's just Meson-to-Meson calling, given that C++ part seems to support Meson now. -- 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
