opam

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.

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.

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.

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.

Minor 1.1 release, fixing the build system to work on OCaml 4.02.0

This minor 1.1 release backports the build system from the upcoming 1.2, fixing several distribution issues.

This minor 1.1 release backports the build system from the upcoming 1.2, fixing several distribution issues.

This release features mostly stability and UI/doc improvements, but also focuses on improving the API and tools to be a better base for the platform (functions for opam-doc, interface with tools like opamfu and opam-installer).

See the CHANGELOG.

This release features mostly bug-fixes and UI/doc improvements, but also focuses on improving the API and tools to be a better base for the platform (functions for opam-doc, interface with tools like opamfu and opam-installer).

This version features several bug-fixes over the September beta release, and
quite a few stability and usability improvements. Thanks to all beta-testers
who have taken the time to file reports, and helped a lot tackling the
remaining issues.

Since its first official release last March, we have fixed many bugs and added lots of new features and stability improvements.

New features go from more metadata to the package and compiler descriptions, to improved package pin workflow, through a much faster update algorithm.

The goal of the first version of OPAM was to get something released that would provide basic package management facilities to the community, but also be designed with distributed open-source design in mind. To that end, OPAM 1.0 supports a remotes mechanism which lets you combine local development trees with other people's remote Git or Darcs repositories. Whenever opam update is run, all the remotes are refreshed and merged, letting you subscribe to other people's compilers and package trees.

This first version is build-system agnostic in the interests of compatibility with the large existing body of third party external source code, and so can't do much in the way of advanced manipulation of the packages.

OPAM 1.0 has been a great success. Since its release, there have been hundreds of external contributions from the community, and over 1000 packages are now contained within the main package repository!