Kyle Edwards

After doing some research on entry points, I understand them a little better, and have a better idea of how we would go about this. The entry point would look...

> There is also `auditwheel` that can potentially move (or rather copy) dependencies into `.libs` folder. Any idea on how to integrate with that, e.g. how to avoid doubling the...

No. `*_ROOT` specifies a prefix to search through various subdirectories (`lib`, `lib64`, `lib/cmake`, etc.) while `*_DIR` specifies *exactly* where to find the file. We know exactly where the file is...

> We've been supporting directly specifying the directory and not requiring an entry point function. How? How does the consuming project find the directly-specified directory?

> I don't believe there is a functionality for the former Right. I'm proposing adding functionality for this: > the installed package defines what and where `Config.cmake` it provides so...

This sounds fine to me. Updating the logic in rapids-cmake with this exception should be pretty straightforward.

Hmmm. I see now that `getConfigFile()` is using `mediaType: { format: "raw" }`. If we add this feature, we'll need to change that in order to get the `html_url` field.