Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Package request: raft, libraft, pylibraft #26600

Open
2 tasks done
h-vetinari opened this issue Jun 8, 2024 · 3 comments
Open
2 tasks done

Package request: raft, libraft, pylibraft #26600

h-vetinari opened this issue Jun 8, 2024 · 3 comments

Comments

@h-vetinari
Copy link
Member

Package name

raft

Package version

Newest

Package website

https://github.com/rapidsai/raft

Package availability

Github

Additional comments

Saw this is used in faiss and (after looking) a couple more rapids-related places. It did get mentioned in #14546 & #21901, where the former noted:

Our CMakeLists.txt looks for it, and one of our header-only build dependencies (raft) includes it,

However, based on the upstream readme, there's also some compiled C++ code and python bindings:

arch

Package is not available

  • The package is not available on conda-forge.

No previous issues or open PRs

  • No previous issue exists and no PR has been opened.
@h-vetinari
Copy link
Member Author

CC @conda-forge/libcugraph @conda-forge/libcublas == @conda-forge/cuda, if you have any inputs here that would be much appreciated.

@leofang
Copy link
Member

leofang commented Jun 8, 2024

RAPIDS folks on the cuda team might be able to give advices. I am not familiar with RAFT's build system and packaging approach.

@vyasr
Copy link
Contributor

vyasr commented Jun 11, 2024

It looks like the libcugraph feedstock has been archived. Personally I wasn't even aware that we had put this on conda-forge at one point. raft is currently in the process of being split into two libraries raft and cuvs (see the README for some info), and I suspect that after that split is complete FAISS will almost entirely rely on the latter. Meanwhile, raft will become a header-only library, so it may be less important to package since it could also be reliably fetched from source during a build (e.g. via Bazel or CMake). I'm not sure if anything else on conda-forge right now makes use of raft. As a result, I'd probably advocate waiting on taking any action here until the raft split is completed and we can more carefully evaluate exactly what is needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

3 participants