[QST] Why is raft not something that is installed like a utils library we can all use? about raft HOT 3 CLOSED

@felipeblazing I think you've been in contact with @cjnolet for this, but wanted to leave a response for reference of anyone else having this question.

For now, RAFT has been designed as source-only/header only (both Python and C++). The source code is meant to be included in the consuming code bases without creating an additional conda package (this design was done mainly by the cuML and cuGraph teams to avoid version conflict headaches between the projects). So it is more similar to say cutlass/cub than it is to cuml/cudf. So there is no standalone binary that needs to be created for RAFT (at the moment I'm writing this), and it is meant to be consumed at build time (not runtime), either by git submodules, CMake git cloning and setup.py build as is described in https://github.com/rapidsai/raft/blob/branch-0.15/BUILD.md#usage-of-raft-by-downstream-projects. So the fact that there is a cuml.raft and a cugraph.raft (that might not point to the same commit in RAFT) is by design.

Note that RAPIDS 0.15 is the first version where we will be adding and using significant functionality in RAFT, so the design/build/distribution process might be adjusted depending on how things work, community feedback, and whatnot.

from raft.

This issue has been marked rotten due to no recent activity in the past 90d. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed.

from raft.

This issue has been marked stale due to no recent activity in the past 30d. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be marked rotten if there is no activity in the next 60d.

from raft.