Daniel Holth

I've add a two-file scheme to this CEP. Instead of trying to update repodata.json each time, we accumulate patches in a simple overlay. It will be a while before (re-)writing...

Yes. Although we could format repodata.json in exactly the same way as conda-index, that formatting is not guaranteed. Instead, we store the hash that the server found when creating the...

Yes, we could do that in the future but in the meantime we are allowed to change this code https://github.com/conda/conda-index/blob/main/conda_index/index/__init__.py#L825-L833 without breaking clients.

So .conda packages are ZIP-format containers with a metadata.json file containing just the version number, and then an info and pkg file that are always .tar.zst even though some earlier...

I don't think the normal way of creating `.conda` can create clobbered files. It takes a list of filenames and categorizes them into two groups. The check would need to...

One thing about this is that when you start using alternative formats (.zst, .jlap) the remote headers last-modified, etag, cache-control come from the alternate file.

An example of the current jlap branch's `.state.json`. `have` is the nominal hash (what the hash of the original repodata.json was according to jlap) `have_hash` is the actual hash on...

In the existing format `"_url": "https://conda.anaconda.org/conda-forge/osx-arm64",` doesn't contain the filename. May want to continue doing that especially since different repodata variants matter. Or ignore the field.

@wolfv do you mean https://github.com/wolfv/ceps/pull/1

If we are going to play with nanoseconds, let's go ahead and replace all timestamps (except those that are web server headers) with those numbers. e.g. last_checked. We will quickly...