Daniel Martí

> or, as a hierarchy, `go clean cache/modules`. note that this prompted me to file https://github.com/cue-lang/cue/issues/3139.

With #3139 implemented, I think we should support the following commands to clean `${CUE_CACHE_DIR}`: * `cue clean all` - clear all caches * `cue clean mod` - clear all module...

@ysmaoui this issue is still open - `cue clean` has not been added as a command yet.

Yes, the files are marked read-only to discourage users from directly modifying them. This is why we want to add a `cue clean` command - to make it easy to...

@snuxoll we borrowed this idea from Go - out of curiosity, do you see issues on MacOS with the Go cache directories as well?

It's true that different registries may serve different source for the same module path and version, but in practice that should be rare and discouraged, given that module import paths...

In the form of a testscript: ``` # evalv2 env CUE_EXPERIMENT=evalv3=0 exec cue export in.cue # evalv3 env CUE_EXPERIMENT=evalv3=1 exec cue export in.cue -- in.cue -- import "list" out: list.Contains(["no",...

How did you try finding these packages in the central registry? If you tried searching, that probably didn't work, given that our search is rather basic at the moment, and...

Sounds good to me. This seems like a recent addition to Docker (https://github.com/docker/cli/pull/6008) so that's why we don't support it yet. How should this work in terms of precedence? That...

Understood. I think the merging could potentially be problematic if we wanted to write any of this config back to disk, but luckily we treat `${DOCKER_CONFIG}/config.json` as read-only, so it...