Matthew R. Becker
Matthew R. Becker
Yep. Correct @jjhelmus. I've checked defaults and conda-forge for violations. IMHO tools should simply fail.
Yeah I am not so sure. The eventual CEP specifying what standard HTTP-based conda server looks like will want a way to specify that subsets of packages on a channel...
We can specify parsing from right to left? > my.server.org/label/label/linux-64/linux-64/repodata.json 1. The last thing is repodata.json 2. So the subdir has to come next (it is "linux-64"). We're left with...
By the logic above, this string > my.server.org/label/linux-64/linux-64/repodata.json would be parsed as 0. remove the repodata.json 1. subdir = linux-64 2. Splitting `my.server.org/label/linux-64/` on the first `label` from the right...
Yep @chenghlee. If you split on the `label` and the label you extract is the empty string, then there is no label and the channel is as you say, `https://my.server.org/label`.
Just to be very clear, in this spec the channel should include everything to the start of the URI. conda itself can strip the anaconda.org out of that bit for...
Right. We can fix that in the cli. That is a display issue.
From @chenghlee's test I think we keep everything including the ports, right?
I need to read those rfcs. I don't know the difference myself.
I think we can defer some of the mapping issues to a spec on mirroring and a global index of channels. I should reframe the OCI cep to simply specify...