[
https://issues.apache.org/jira/browse/ARROW-17347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17577482#comment-17577482
]
Will Jones commented on ARROW-17347:
------------------------------------
We may also wish to mention the bundled dependencies, and explain why they are
generally a last resort. See also discussion:
https://lists.apache.org/thread/hgory6jkqg2vcqsw36635gsqcvkgk45z
> [C++][Docs] Describe limitations and alternatives for handling dependencies
> via package managers
> ------------------------------------------------------------------------------------------------
>
> Key: ARROW-17347
> URL: https://issues.apache.org/jira/browse/ARROW-17347
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++, Documentation
> Reporter: Kae Suarez
> Priority: Major
>
> In this page: [https://arrow.apache.org/docs/developers/cpp/building.html] it
> is described how package managers can be used to get dependencies for Arrow.
> My specific experience is with Apple Silicon on macOS, so I can describe my
> experience there. A Brewfile is provided to assist getting necessary packages
> to build Arrow, but it does not include all relevant packages to build the
> most Arrow features possible on Mac (i.e., everything but CUDA). Diving
> further, I learned that Homebrew cannot provide all necessary dependencies
> for features such as GCS support, and had to turn to conda-forge. Upon doing
> so, I started having overlapping dependencies elsewhere, and eventually had
> to turn fully to conda.
> It would be helpful to have the limitations laid out for what features can be
> built with what package managers, as well as adding conda as an alternative
> to Homebrew for macOS users, since that is necessary to build the fullest
> Arrow possible without building other libraries from source as well.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
