'opam list -S' sorts the package by dependency order
Merge branch 'master' of github.com:OCamlPro/opam
Better error message when re-pinning a package to the same thing
Fixed remove order for 'reinstall'
Closes #773, #775 and #776
Merge pull request #783 from AltGr/fix-reinstall-order

Fix reinstall order
Add a `--strict` option, and be more tolerant with opam files when not set
that will make OPAM more forward-compatible with field additions
Closes #784
Merge pull request #785 from AltGr/--strict

Add a `--strict` option, and be more tolerant with opam files when not set
.install files, support for installing in etc.
Merge pull request #791 from dbuenzli/master

.install files, support for installing in etc.
Prettify an information message
Merge branch 'master' of github.com:OCamlPro/opam
'opam config var pkg:pinned' should work even if the package is not installed

Fix #743
Fix the package stats computation

This is related to #793, although not fixing it completely.
[update] Do not fail when a pinned package is not installed
[update] do not display non-installed pinned packages as a DELETED package
Add more debug info
[pin] Remove the dev-package dir when a pinned package do not install properly

Fix #768
Better handling of package removed from upstream
Fixed 'opam install' when some packages have been removed from upstream
Fixed upgrade when packages have been removed from upstream
The solver needs to know about those packages to be able to remove them, which was not the case ;
there is still a glitch if you try eg to reinstall 'a' when 'b' depends on 'a': nothing will be
done about it, since 'b' can't be recompiled. If 'c' depends on 'b', it won't be recompiled either.

But since there is no clear way of handling that situation (the only correct thing would be to remove b and c ; that would need some more work),
it seems reasonable for now to ask for an 'opam upgrade' in such pathological cases.

Closes: #740