R. Boujbel

That's the mystery, why opam failed to remove those files in the first place. See PR #4917, it adds an option to opam clean that removes remaining files not referenced...

Please refer to [discussion](https://github.com/ocaml/opam/discussions/5130) for examples of conflict message.

Good for me (and more consistent about the command itself, its difference with `list`) to keep only installed packages. About dependencies filters, they can be retrieved unfiltered via `st.opams`: `OpamFile.OPAM.depends...

The first one: an entry for `tree`, the other for `why`. We'll need also need to add API changes (addition of modules / changes of signtures, etc. but better once...

oupsy

updated

Thanks all!

Can you precise the use case ? opam display a message when a local switch is already existing, and ask to clean up in case of failing initialisation: ``` $...

Ok, I see better. I'm wondering, on the process, @RyanGibb why/how did you get to create a new switch while you already had one? From what I understand, you wanted...

What about prompting a link to a [FAQ](https://opam.ocaml.org/doc/FAQ.html) entry that summarises all cases (switch to remove and checkout new branch for the moment). The message will be cleaner and it...