[
https://issues.apache.org/jira/browse/ARROW-6715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17262287#comment-17262287
]
Kouhei Sutou commented on ARROW-6715:
-------------------------------------
We can separate nvidia-cuda-toolkit dependency in Apache Arrow C++ core
({{libarrow.so}}) because we implement CUDA depended code as a separated
library, {{libarrow_cuda.so}}.
But Plasma isn't implemented like that. Plasma embeds CUDA depended code in
it's core code. If we want to make nvidia-cuda-toolkit optional for Plasma
packages, we need to build Plasma with/without {{-DARROW_CUDA=ON}} and build
two Plasma packages for with/without CUDA like {{libplasma-dev}} and
{{libplasma-cuda-dev}}. Users must choose one of {{libplasma-dev}} and
{{libpalsma-cuda-dev}}. They can't install both of them at the same time.
I don't want to do this approach because it increases packaging build time...
It's better that Plasma uses the approach that Apache Arrow C++ core uses.
> [Website] Describe "non-free" component is needed for Plasma packages in
> install page
> -------------------------------------------------------------------------------------
>
> Key: ARROW-6715
> URL: https://issues.apache.org/jira/browse/ARROW-6715
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Website
> Reporter: Kouhei Sutou
> Assignee: Kouhei Sutou
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Because Plasma packages depend on nvidia-cuda-toolkit package that in
> non-free component.
> Note that Plasma packages are available only for amd64. Because
> nvidia-cuda-toolkit package isn't available for arm64.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
