Closed dholth closed 9 months ago
I think this is great but what is the usecase for this?
Anaconda is experimenting with having a collection of historical repodata.json pointing at the (supposed to be immutable) set of packages. I could have used this while developing jlap, which also had a test proxy to fetch repodata.json more quickly than conda was able to. Someone might also be interested in subsetting repodata.json for policy reasons.
I wonder if conda would work properly if the package keys were sha hashes so that you could point the whole thing at a content-addressed store instead of a server with normal filenames.
I would love to be able to directly use SHA hashes! At prefix we also use a content-addressable store, but we do the conversion on the server side now (which is a bit of a waste). We could also add a URL to each entry with a download URL. Or we can template the base_url
to be able to construct a complete URL that might also include something other than the filename. WDYT?
In rattler we do assume that the keys (filenames) are properly formatted and sorted for some speed optimizations so just using sha hashes wouldn't work there.
I implemented this CEP in rattler: https://github.com/mamba-org/rattler/pull/322
Should we maybe start a vote on this CEP?
Agreed, this would be awesome to have.
@conda-incubator/steering
This vote falls under the "Enhancement Proposal Approval" policy of the conda governance policy, please vote and/or comment on this proposal at your earliest convenience.
It needs 60% of the Steering Council to vote yes
to pass.
To vote, please leave yes
, no
or abstain
as comments below.
If you have questions concerning the proposal, you may also leave a comment or code review.
This vote will end on 2024-01-18, End of Day, Anywhere on Earth (AoE).
Note: This is an extended voting period to accommodate the start of the year and the complexity of the proposal.
yes
yes
yes
yes
(first repodata_version
bump!)
yes
Yes
Yes
Yes
@CJ-Wright @goanpeca @chenghlee @marcelotrevisani @jakirkham @mbargull @kkraus14 this is a reminder to please vote with YES / NO / ABSTAIN on this CEP :)
Yes!
yes
yes
Yes I am making this comment solely in my personal capacity and am not conveying any rights to any intellectual property of any third parties.
Vote count:
The steering council consists of 15 people. That means, 86% have voted, and 100% have voted yes. This CEP is accepted! 🎉
@dholth any last changes? Otherwise I or @jezdez should probably push the CEP (cep-15.md) to it's final name and merge to the repo.
LGTM, merge it.
Done!
Allow repodata.json and packages to live in separate places.