Official stable release announcements and updates from the OCaml compiler, OCaml infrastructure and the OCaml Platform Tools.
backend:
fake:
'_ type variables.vim:
This release also contains contributions from: Geoff Gole, Rudi Grinberg, Markus Mottl, Roman Vorobets and Arthur Wendling.
backend:
L.m will expand to List.map ; List.m... ; ListLabels.map ; ... if
L doesn't exist.emacs:
misc:
vim:
:Locate command:Renamefileencoding where necessary (#332)Config.load_path as UTop.load_path (Peter Zotov)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 🙈
We are very proud to announce the availability of OPAM 1.2.0.
Simply follow the usual instructions, using your preferred method (package from your distribution, binary, source, etc.) as documented on the homepage.
NOTE: There are small changes to the internal repository format (~/.opam). It will be transparently updated on first run, but in case you might want to go back and have anything precious there, you're advised to back it up.
Lot of work has been put into providing a cleaner interface, with helpful behaviour and messages in case of errors.
The documentation pages also have been largely rewritten for consistency and clarity.
This is just the top of the list:
opam pin command. See the
Simplified packaging workflowopam sourceopam lint command to check the quality of packagesFor more detail, see the announcement for the beta, the full changelog, and the bug-tracker.
The package format has been extended to the benefit of both packagers and users. The repository already accepts packages in the 1.2 format, and this won't affect 1.1 users as a rewrite is done on the server for compatibility with 1.1.
If you are hosting a repository, you may be interested in these administration scripts to quickly take advantage of the new features or retain compatibility.
Oops, we went looking but didn't find the changelog for this release 🙈
After a few months of development, we are pleased to announce the stable release of Merlin 2.0. Supported OCaml versions range from 4.00.1 to 4.02.1.
Merlin is a tool focused on helping you code in OCaml by providing features such as:
We provide integration into Vim and Emacs. An external plugin is also available for Sublime Text.
This release provides great improvements in robustness and quality of analysis. Files that changed on disk are now automatically reloaded. The parsing process is finer grained to provide more accurate recovery and error messages. Integration with Jane Street Core and js_of_ocaml has also improved.
Vim & Emacs are still the main targeted editors. Thanks to Luc Rocher, preliminary support for Sublime Text is also available, see Sublime-text-merlin. Help is welcome to improve and extend supported editing environments.
Windows support also received some fixes. Merlin is now distributed in WODI. Integration in OCaml-on-windows is planned.
This new version of Merlin is already available with opam using opam install merlin, and can also be built from the sources which are available at
the-lambda-church/merlin.
This is a major release which we worked on for several months, rewriting many parts of the codebase. An exhaustive list of changes is therefore impossible to give, but here are some key points (from an user perspective):
This release also contains contributions from: Yotam Barnoy, Jacques-Pascal Deplaix, Geoff Gole, Rudi Grinberg, Steve Purcell and Jan Rehders.
We also thank Gabriel Scherer and Jane Street for their continued support.
Minor update to installation procedure
Oops, we went looking but didn't find the changelog for this release 🙈
This release also marks the apparition of a proper opam install script.
backend:
documentation:
emacs:
vim:
Most package managers support some pin functionality to ensure that a given package remains at a particular version without being upgraded. The stable OPAM 1.1 already supported this by allowing any existing package to be pinned to a target, which could be a specific released version, a local filesystem path, or a remote version-controlled repository.
However, the OPAM 1.1 pinning workflow only lets you pin packages that already exist in your OPAM repositories. To declare a new package, you had to go through creating a local repository, registering it in OPAM, and adding your package definition there. That workflow, while reasonably clear, required the user to know about the repository format and the configuration of an internal repository in OPAM before actually getting to writing a package. Besides, you were on your own for writing the package definition, and the edit-test loop wasn't as friendly as it could have been.
A natural, simpler workflow emerged from allowing users to pin new package names that don't yet exist in an OPAM repository:
opam pin add in the development source treeTo make it even easier, OPAM can now interactively help you write the package definition, and you can test your updates with a single command. This blog post explains this new OPAM 1.2 functionality in more detail; you may also want to check out the new Packaging tutorial relying on this workflow.
For illustration purposes in this post I'll use a tiny tool that I wrote some time ago and never released: ocp-reloc. It's a simple binary that fixes up the headers of OCaml bytecode files to make them relocatable, which I'd like to release into the public OPAM repository.
The command opam pin add <name> <target> pins package <name> to
<target>. We're interested in pinning the ocp-reloc package
name to the project's source directory.
cd ocp-reloc
opam pin add ocp-reloc .
If ocp-reloc were an existing package, the metadata would be fetched from
the package description in the OPAM repositories. Since the package doesn't yet exist,
OPAM 1.2 will instead prompt for on-the-fly creation:
Package ocp-reloc does not exist, create as a NEW package ? [Y/n] y
ocp-reloc is now path-pinned to ~/src/ocp-reloc
NOTE: if you are using beta4, you may get a version-control-pin instead, because we added auto-detection of version-controlled repos. This turned out to be confusing (issue #1582), because your changes wouldn't be reflected until you commit, so this has been reverted in favor of a warning. Add the
--kind pathoption to make sure that you get a path-pin.
Now your package still needs some kind of definition for OPAM to acknowledge it;
that's where templates kick in, the above triggering an editor with a pre-filled
opam file that you just have to complete. This not only saves time in
looking up the documentation, it also helps getting consistent package
definitions, reduces errors, and promotes filling in optional but recommended
fields (homepage, etc.).
opam-version: "1.2"
name: "ocp-reloc"
version: "0.1"
maintainer: "Louis Gesbert <louis.gesbert@ocamlpro.com>"
authors: "Louis Gesbert <louis.gesbert@ocamlpro.com>"
homepage: ""
bug-reports: ""
license: ""
build: [
["./configure" "--prefix=%{prefix}%"]
[make]
]
install: [make "install"]
remove: ["ocamlfind" "remove" "ocp-reloc"]
depends: "ocamlfind" {build}
After adding some details (most importantly the dependencies and
build instructions), I can just save and exit. Much like other system tools
such as visudo, it checks for syntax errors immediately:
[ERROR] File "/home/lg/.opam/4.01.0/overlay/ocp-reloc/opam", line 13, character 35-36: '.' is not a valid token.
Errors in /home/lg/.opam/4.01.0/overlay/ocp-reloc/opam, retry editing ? [Y/n]
You probably want to try your brand new package right away, so
OPAM's default action is to try and install it (unless you specified -n):
ocp-reloc needs to be installed.
The following actions will be performed:
- install cmdliner.0.9.5 [required by ocp-reloc]
- install ocp-reloc.0.1*
=== 1 to install ===
Do you want to continue ? [Y/n]
I usually don't get it working the first time around, but opam pin edit ocp-reloc and opam install ocp-reloc -v can be used to edit and retry until
it does.
How do you keep working on your project as you edit the source code, now that you are installing through OPAM? This is as simple as:
opam upgrade ocp-reloc
This will pick up changes from your source repository and reinstall any packages
that are dependent on ocp-reloc as well, if any.
So far, we've been dealing with the metadata locally used by your OPAM
installation, but you'll probably want to share this among developers of your
project even if you're not releasing anything yet. OPAM takes care of this
by prompting you to save the opam file back to your source tree, where
you can commit it directly into your code repository.
cd ocp-reloc
git add opam
git commit -m 'Add OPAM metadata'
git push
The above information is sufficient to use OPAM locally to integrate new code into an OPAM installation. Let's look at how other developers can share this metadata.
If another developer wants to pick up ocp-reloc, they can directly use
your existing metadata by cloning a copy of your repository and issuing their
own pin.
git clone git://github.com/OCamlPro/ocp-reloc.git
opam pin add ocp-reloc/
Even specifying the package name is optional since this is documented in
ocp-reloc/opam. They can start hacking, and if needed use opam pin edit to
amend the opam file too. No need for a repository, no need to share anything more than a
versioned opam file within your project.
We have been focusing on an unreleased package, but the same
functionality is also of great help in handling existing packages, whether you
need to quickly hack into them or are just curious. Let's consider how to
modify the omd Markdown library.
opam source omd --pin
cd omd.0.9.7
...patch...
opam upgrade omd
The new opam source command will clone the source code of the library you
specify, and the --pin option will also pin it locally to ensure it is used
in preference to all other versions. This will also take care of recompiling
any installed packages that are dependent on omd using your patched version
so that you notice any issues right away.
There's a new OPAM field available in 1.2 called
dev-repo. If you specify this in your metadata, you can directly pin to the upstream repository viaopam source --dev-repo --pin.
If the upstream repository for the package contains an opam file, that file will be picked up
in preference to the one from the OPAM repository as soon as you pin the package.
The idea is to have:
opam file that is versioned along with your source code
(and thus accurately tracks the latest dependencies for your package).opam file that is published on the OPAM repository and can
be updated independently without making a new release of the source code.How to get from the former to the latter will be the subject of another post! In the meantime, all users of the beta are welcome to share their experience and thoughts on the new workflow on the bug tracker.
backend:
emacs:
C-c l previously bound to merlin-useC-c r previously bound to merlin-restart-processC-c t previously bound to merlin-type-exprC-<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 #loadWe 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)Toplooputop-fullOops, 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