You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Wes McKinney (JIRA)" <ji...@apache.org> on 2018/08/30 20:14:00 UTC

[jira] [Commented] (ARROW-3149) [C++] Use gRPC (when it exists) from conda-forge for CI builds

    [ https://issues.apache.org/jira/browse/ARROW-3149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16597882#comment-16597882 ] 

Wes McKinney commented on ARROW-3149:
-------------------------------------

Here is a partially complete recipe: https://github.com/AnacondaRecipes/grpcio-feedstock/tree/master/recipe. The vendoring situation with gRPC makes things pretty complicated -- the CMake build for example installs all of the transitive dependencies. It seems that the patch here is intended to undo this logic; there may be some other way to avoid installing the vendored dependencies without having to patch the CMakeLists.txt (which could grow unmaintainable)

> [C++] Use gRPC (when it exists) from conda-forge for CI builds
> --------------------------------------------------------------
>
>                 Key: ARROW-3149
>                 URL: https://issues.apache.org/jira/browse/ARROW-3149
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: C++
>            Reporter: Wes McKinney
>            Priority: Major
>             Fix For: 0.12.0
>
>
> gRPC is not available in conda-forge yet. It has a rather complex dependency chain if you want secure RPCs (e.g. Google is maintaining a fork of OpenSSL, BoringSSL). Some of these dependencies will have to be added to conda-forge in turn.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)