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.

Sign up for GitHub

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

Jump to bottom

Epic: how do installers use data from metadata provider to map to files in a repo/index #6

Open

msarahan opened this issue Aug 1, 2024 · 0 comments

Contributor

msarahan commented Aug 1, 2024 •

edited

Loading

Following #5, once we have variant metadata on-hand somehow, how should it get used to resolve variant files?

Some ideas that have been mentioned:

Resolve a package without considering variant info, then collect variants and pick the right one
Resolve variants prior to current "normal" resolution process. Treat variants as "mini-repos", similar to how pytorch does.
(more, I need to go through the threads to collect these)

msarahan added this to Extending Metadata

msarahan converted this from a draft issue

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