1.2.1~beta

This patch-version over 1.2.0 brings lots of fixes and a rewritten action and parallel processing engine. Although visible mostly in the messages displayed, this will bring a big improvement on reliability and predictability. It should also be faster.

Note that older versions disabled parallelism at init by default. If you want to benefit from it, you may want to change the jobs field in ~/.opam/config.

There is no format change in this version. However, it will mark ~/.opam/config as 1.2.1, after which OPAM 1.2.0 may complain. You can safely revert the field to 1.2.0 in that case, if you need to switch back.

Summary of the changes

• Non-system compiler definitions without source are now allowed
• Stronger handling of compiler "base" packages, they can't be removed anymore
• Rewritten action resolution mechanism to be based on atomic actions.
  Actions are not aborted anymore on first failure when there is no
  dependency.
• Rewritten parallel command execution engine
• Better display of actions, lots of improved messages
• opam upgrade pkg now fails if no new version of pkg can be installed
• fixed shell configuration for various shells
• Updated Dose dependency to 3.3
• Fixed behaviour of opam switch and related commands when a switch
  is locally set in a shell (through OPAMSWITCH)
• Better behaviour on failed opam switch
• New pinning mode, set by default on local VC repos: use current file
  tree, but limited to version-tracked files.
• Faster and cleaner handling of downloads
• Now compiles with --safe-string on OCaml 4.02, better compatibility handling
• opam unpin now accepts multiple arguments
• opam pin add <pkg>.<version> <target> is now allowed to specify
  the advertised version
• Fixed bug leading to a bad CAML_LD_LIBRARY_PATH when switching from system
• Better opam lint, reporting warnings and errors, including format errors
• opam config setup now takes --shell= instead of --sh, --csh, --fish, --zsh
• Lots of bug-fixes

Closed issues

https://github.com/ocaml/opam/issues?q=closed%3A%3E2014-10-16+

1.2.0 Release

This version introduces many new features and lots of improvement, mostly related to UI and stability, and a new, integrated development workflow.

See the full changelog at https://raw.githubusercontent.com/ocaml/opam/1.2.0/CHANGES

Important note

There are small changes in the repository format, your .opam/ will be automatically updated on first run.
Back it up if you may need to roll back to an older OPAM version.

Fourth Release Candidate for 1.2.0

This RC has been promoted to 1.2.0.

Third Release Candidate for 1.2.0

This version introduces many new features and lots of improvement, mostly related to UI and stability, and a new, integrated development workflow.

Important note

There are small changes in the repository format, your .opam/ will be automatically updated on first run. Be careful to backup if you intend to try out the new version and switch back

Second Release Candidate for 1.2.0

This version introduces many new features and lots of improvement, mostly related to UI and stability, and a new, integrated development workflow.

Important note

There are small changes in the repository format, your .opam/ will be automatically updated on first run. Be careful to backup if you intend to try out the new version and switch back

First Release Candidate for 1.2.0

This version introduces many new features and lots of improvement, mostly related to UI and stability, and a new, integrated development workflow.

Important note

There are small changes in the repository format, your .opam/ will be automatically updated on first run. Be careful to backup if you intend to try out the new version and switch back

Fourth beta for the 1.2 release

This version introduces many new features and lots of improvement, mostly related to UI and stability, and a new, integrated development workflow.

Important notes

• There are small changes in the repository format, your .opam/ will be automatically updated on first run. Be careful to backup if you intend to try out the new version and switch back
• If you were using a recent git snapshot, opam 1.2.0~beta may complain that your local repo is version 1.2.0 which is higher than 1.2.0~beta. You can fix it by editing the opam-version field in .opam/config or setting OPAMSKIPVERSIONCHECKS=1.

Third beta for the 1.2 release

This version introduces many new features and lots of improvement, mostly related to UI and stability, and the new, integrated development workflow.

Important notes

• There are small changes in the repository format, your .opam/ will be automatically updated on first run. Be careful to backup if you intend to try out the new version and switch back
• If you were using a recent git snapshot, opam 1.2.0~beta may complain that your local repo is version 1.2.0 which is higher than 1.2.0~beta. You can fix it by editing the opam-version field in .opam/config or setting OPAMSKIPVERSIONCHECKS=1.

Second beta for the 1.2 release

BROKEN: stick to beta1 for now

This version introduces many new features and lots of improvement, mostly related to UI and stability, and the new, integrated development workflow.

Important notes

• There are small changes in the repository format, your .opam/ will be automatically updated on first run. Be careful to backup if you intend to try out the new version and switch back
• If you were using a recent git snapshot, opam 1.2.0~beta may complain that your local repo is version 1.2.0 which is higher than 1.2.0~beta. You can fix it by editing the opam-version field in .opam/config or setting OPAMSKIPVERSIONCHECKS=1.

First beta for the 1.2.0 release

This version introduces many new features and lots of improvement, mostly related to UI and stability, and the new, integrated development workflow.

Important notes

• There are small changes in the repository format, your .opam/ will be automatically updated on first run. Be careful to backup if you intend to try out the new version and switch back
• If you were using a recent git snapshot, opam 1.2.0~beta may complain that your local repo is version 1.2.0 which is higher than 1.2.0~beta. You can fix it by editing the opam-version field in .opam/config or setting OPAMSKIPVERSIONCHECKS=1.