See full changelog
- fix compatibility with OCaml 4.00.1 and earlier
Read the latest releases and updates from the OCaml compiler, OCaml infrastructure and the OCaml Platform Tools.
backend:
emacs:
C-c l
previously bound to merlin-use
C-c r
previously bound to merlin-restart-process
C-c t
previously bound to merlin-type-expr
C-<up>
and C-<down>
as these already have a
meaning in emacs ( #129 )
They were bound to merlin-type-enclosing-go-up
and
merlin-type-enclosing-go-down
respectively.extensions:
vim:
Async_core
to
Async_kernel
#load_rec
the same way as #load
We are proud to announce that OPAM 1.1.1 has just been released.
This minor release features mostly stability and UI/doc improvements over
OPAM 1.1.0, 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
). Lots of bigger changes are in the works, and
will be merged progressively after this release.
Installation instructions are available on the wiki.
Note that some packages may take a few days until they get out of the pipeline. If you're eager to get 1.1.1, either use our binary installer or compile from source.
The 'official' package repository is now hosted at opam.ocaml.org, synchronised with the Git repository at http://github.com/ocaml/opam-repository, where you can contribute new packages descriptions. Those are under a CC0 license, a.k.a. public domain, to ensure they will always belong to the community.
Thanks to all of you who have helped build this repository and made OPAM such a success.
From the changelog:
opam-admin make <packages> -r
(#990)opam-admin depexts
(#997)OpamSolver.empty_universe
for flexible universe instantiation (#1033)OpamFormula.eval_relop
and OpamFormula.check_relop
(#1042)OpamCompiler.compare
to match Pervasives.compare
(#1042)OpamCompiler.eval_relop
(#1042)OpamPackage.Name.compare
(#1046)version_constraint
and version_formula
to OpamFormula
(#1046)info
an alias for show
and added the alias
uninstall
(#944)opam init --root=<relative path>
(#1047)opam info
(#1052).install
files usable outside of opam (#1026)--resolve
option to opam-admin make
that builds just the archives you need for a specific installation (#1031)which
by a more portable call (#1061)opam config report
to help with bug reports (#1034)opam upgrade <pkg>
(#1001)opam init
to a non-empty root directory (#974)backend:
emacs:
extensions
vim:
-require
command line argument to specify packages on the
command line$OCAML_TOPLEVEL_PATH/autoload
at
startup. Can be disabled with autoload: false
in ~/.utoprc
or
-no-autoload
.#typeof
to values and modules. Thanks to Thomas Refis for
this feature#utop_prompt_XXX
#require
when passing multiple packages#
to $
to match the standard
toplevelUTop.show_box
to allow one to hide the completion
bar_
. This can be disabled with
UTop.set_hide_reserved false
.Enter
in the middle of a comment-short-paths
options for OCaml >= 4.01.0
(and make it the default)Toploop
utop-full
Oops, we went looking but didn't find the changelog for this release 🙈
Oops, we went looking but didn't find the changelog for this release 🙈
Oops, we went looking but didn't find the changelog for this release 🙈
Oops, we went looking but didn't find the changelog for this release 🙈
Oops, we went looking but didn't find the changelog for this release 🙈
Oops, we went looking but didn't find the changelog for this release 🙈
Oops, we went looking but didn't find the changelog for this release 🙈
After a while staged as RC, we are proud to announce the final release of OPAM 1.1.0!
Thanks again to those who have helped testing and fixing the last few issues.
The repository format has been improved with incompatible new features; to account for this, the new repository is now hosted at [opam.ocaml.org][], and the legacy repository at [opam.ocamlpro.com][] is kept to support OPAM 1.0 installations, but is unlikely to benefit from many package updates. Migration to [opam.ocaml.org][] will be done automatically as soon as you upgrade your OPAM version.
You're still free, of course, to use any third-party repositories instead or in addition.
NOTE: When switching from 1.0, the internal state will need to be upgraded.
THIS PROCESS CANNOT BE REVERTED. We have tried hard to make it fault-
resistant, but failures might happen. In case you have precious data in your
~/.opam
folder, it is advised to backup that folder before you upgrade
to 1.1.0.
Using the binary installer:
Using the .deb packages from Anil's PPA (binaries are [currently syncing][1]): add-apt-repository ppa:avsm/ppa apt-get update sudo apt-get install opam
For OSX users, the homebrew package will be updated shortly.
or build it from sources at :
OPAM is a source-based package manager for OCaml. It supports multiple simultaneous compiler installations, flexible package constraints, and a Git-friendly development workflow. OPAM is edited and maintained by OCamlPro, with continuous support from OCamlLabs and the community at large (including its main industrial users such as Jane-Street and Citrix).
The 'official' package repository is now hosted at [opam.ocaml.org][], synchronised with the Git repository at [http://github.com/ocaml/opam-repository][repo], where you can contribute new packages descriptions. Those are under a CC0 license, a.k.a. public domain, to ensure they will always belong to the community.
Thanks to all of you who have helped build this repository and made OPAM such a success.
Too many to list here, see https://raw.github.com/OCamlPro/opam/1.1.0/CHANGES
For packagers, some new fields have appeared in the OPAM description format:
depexts
provides facilities for dealing with system (non ocaml) dependenciesmessages
, post-messages
can be used to notify the user eg. of licensing information,
or help her troobleshoot at package installation.available
supersedes ocaml-version
and os
constraints, and can contain
more expressive formulasAlso, we have integrated the main package repository with Travis, which will help us to improve the quality of contributions (see Anil's post).
documentation:
emacs:
vim:
backend:
documentation:
emacs
Minor release, but merlin is now compatible with ocaml versions > 4.00.1. The only noticeable changes since 1.3 is the use of short paths even with version 4.00.1 of ocaml.
Oops, we went looking but didn't find the changelog for this release 🙈
backend:
emacs:
extensions:
misc:
vim:
I am very happy to announce the first official release of OPAM!
Many of you already know and use OPAM so I won't be long. Please read http://www.ocamlpro.com/blog/2013/01/17/opam-beta.html for a longer description.
1.0.0 fixes many bugs and add few new features to the previously announced beta-release.
The most visible new feature, which should be useful for beginners with
OCaml and OPAM, is an auto-configuration tool. This tool easily enables all
the features of OPAM (auto-completion, fix the loading of scripts for the
toplevel, opam-switch-eval alias, etc). This tool runs interactively on each
opam init
invocation. If you don't like OPAM to change your configuration
files, use opam init --no-setup
. If you trust the tool blindly, use
opam init --auto-setup
. You can later review the setup by doing
opam config setup --list
and call the tool again using opam config setup
(and you can of course manually edit your ~/.profile (or ~/.zshrc for zsh
users), ~/.ocamlinit and ~/.opam/opam-init/*).
Please report:
Packages for Debian and OSX (at least homebrew) should follow shortly and I'm looking for volunteers to create and maintain rpm packages. The binary installer is up-to-date for Linux and Darwin 64-bit architectures, the 32-bit version for Linux should arrive shortly.
If you want to build from sources, the full archive (including dependencies) is available here:
http://www.ocamlpro.com/pub/opam-full-latest.tar.gz
If you are upgrading from 0.9.* you won't have anything special to do apart
installing the new binary. You can then update your package metadata by
running opam update
. If you want to use the auto-setup feature, remove the
"eval opam config env
line you have previously added in your ~/.profile
and run opam config setup --all
.
So everything should be fine. But you never know ... so if something goes horribly wrong in the upgrade process (of if your are upgrading from an old version of OPAM) you can still trash your ~/.opam, manually remove what OPAM added in your ~/.profile (~/.zshrc for zsh users) and ~/.ocamlinit, and start again from scratch.
Great success on github. Thanks everybody for the great contributions!
https://github.com/OCamlPro/opam: +2000 commits, 26 contributors https://github.com/OCamlPro/opam-repository: +1700 commits, 75 contributors, 370+ packages
on http://opam.ocamlpro.com/ +400 unique visitor per week, 15k 'opam update' per week +1300 unique visitor per month, 55k 'opam update' per month 3815 unique visitor since the alpha release
The full change-log since the beta release in January:
1.0.0 [Mar 2013]
0.9.6 [Mar 2013]
~/.profile
when using dash (eg. in Debian/Ubuntu)0.9.5 [Mar 2013]
opam remove <pkg> --keep-build-dir
keeps the folder if a source archive is extractedopam config exec "CMD ARG1 ... ARGn" --switch=SWITCH
to execute a command in a subshellopam update
wrt. pinned packagesopam config setup
)~/.ocamlinit
when running opam init
0.9.4 [Feb 2013]
-a
type
instead of which
to detect existing commands)depends
and depopts
fields in opam info
opam info pkg.version
shows the metadata for this given package versiondoc
fields in .install
filesopam list
now only shows installable packages0.9.3 [Feb 2013]
0.9.2 [Jan 2013]
opam repo remove repo-name
opam config env
opam-foo
scripts (which can be called using opam foo
)0.9.1 [Jan 2013]