…hanged upstream" This means we do nothing if the 'opam' file has changed, which means: we can now modify 'opam' files without fear (eg. we can add more metadata when we need it). This should fix #497
…ince 0.9.0" This reverts commit 40ef748.
Add an option to enable --autoremove when removing packages (by default it's off). You can also enable it by setting OPAMAUTOREMOVE. The semantics is the following: * `opam remove <pkg>` will simply remove the package * `opam remove <pkg> -a` will remove the package and its dependencies * `opam remove -a` will remove all the packages which have not been explicitely installed (note: you can do `opam install <pkg>` to an already installed package to make it become a 'root' package which will not be uninstalled using `-a`).
The is related to #488
So now: 'opam install <pkg>' add <pkg> to the list of root packages even if <pkg> is already installed.
This can be useful when substituting variables in .opam files.
This should fix #432
Remark: if you find 'repository' too long, you can use 'opam repo' instead (as cmdliner looks for matching commands with the same prefix)