内容简介:We are happy to announce the alpha release of Opam 2.1.0, one year and a half after Opam 2.0.0.Many new features made it in (see theThe two following features have been around for a while as plugins and are now completely integrated in the core of opam. No
We are happy to announce the alpha release of Opam 2.1.0, one year and a half after Opam 2.0.0.
Many new features made it in (see the complete changelog or release note for the details), but here are a few highlights of this release.
Release highlights
The two following features have been around for a while as plugins and are now completely integrated in the core of opam. No extra installs needed anymore, and a more smooth experience.
Seamless integration of System dependencies handling (a.k.a. “depexts”)
A number of opam packages depend on tools or libraries installed on the system, which are out of the scope of opam itself. Previous versions of opam added a specification format , and opam 2.0 already handled checking the OS and extracting the required system package names.
However, the workflow generally involved letting opam fail once, then installing the dependencies and retrying, or explicitely using the opam-depext plugin , which was invaluable for CI but still incurred extra steps.
With opam 2.1.0, depexts are seamlessly integrated, and you basically won’t have to worry about them ahead of time:
-
Before applying its course of actions, opam 2.1.0 checks that external dependencies are present, and will prompt you to install them. You are free to let it do it using
sudo
, or just run the provided commands yourself. - It is resilient to depexts getting removed or out of sync.
- Opam 2.1.0 detects packages that depend on stuff that is not available on your OS version, and automatically avoids them.
This is all fully configurable, and can be bypassed without tricky commands when you need it ( e.g. when you compiled a dependency yourself).
Dependency locking
To share a project for development, it is often necessary to be able to reproduce the exact same environment and dependencies setting — as opposed to allowing a range of versions as opam encourages you to do for releases.
For some reason, most other package managers call this feature “lock files”. Opam can handle those in the form of [foo.]opam.locked
files, and the --locked
option.
With 2.1.0, you no longer need a plugin to generate these files: just running opam lock
will create them for existing opam
files, enforcing the exact version of all dependencies (including locally pinned packages).
If you check-in these files, new users would just have run opam switch create . --locked
on a fresh clone to get a local switch ready to build the project.
Pinning sub-directories
This one is completely new: fans of the Monorepo rejoice, opam is now able to handle projects in subtrees of a repository.
-
Using
opam pin PROJECT_ROOT --subpath SUB_PROJECT
, opam will look forPROJECT_ROOT/SUB_PROJECT/foo.opam
. This will behave as a pinning toPROJECT_ROOT/SUB_PROJECT
, except that the version-control handling is done inPROJECT_ROOT
. -
Use
opam pin PROJECT_ROOT --recursive
to automatically lookup all sub-trees with opam files and pin them.
Opam switches are now defined by invariants
Previous versions of opam defined switches based on base packages , which typically included a compiler, and were immutable. Opam 2.1.0 instead defines them in terms of an invariant , which is a generic dependency formula.
This removes a lot of the rigidity opam switch
commands had, with little changes on the existing commands. For example, opam upgrade ocaml
commands are now possible; you could also define the invariant as ocaml-system
and have its version change along with the version of the OCaml compiler installed system-wide.
Configuring opam from the command-line
The new opam option
command allows to configure several options, without requiring manual edition of the configuration files.
For example:
-
opam option jobs=6 --global
will set the number of parallel build jobs opam is allowed to run (along with the associatedjobs
variable) -
opam option depext-run-commands=false
disables the use ofsudo
for handling system dependencies; it will be replaced by a prompt to run the installation commands.
The command opam var
is extended with the same format, acting on switch and global variables.
Try it!
In case you plan a possible rollback, you may want to first backup your ~/.opam
directory.
The upgrade instructions are unchanged:
-
Either from binaries: run
sh <(curl -sL https://raw.githubusercontent.com/ocaml/opam/master/shell/install.sh) --dev
or download manually from the Github “Releases” page to your PATH.
-
Or from source, using opam:
opam update; opam install opam-devel
- Or from source, manually: see the instructions in the README .
You should then run:
opam init --reinit -ni
This is still a alpha, so a few glitches or regressions are to be expected. Please report them to the bug-tracker . Thanks for trying it out, and hoping you enjoy!
NOTE: this article is cross-posted on opam.ocaml.org andocamlpro.com. Please head to the latter for the comments!
About OCamlPro
OCamlPro is a company founded in 2011, with the mission to help industrial users benefit from state-of-the art programming languages like OCaml and Rust. We design, create and implement custom ad-hoc software for our clients. We also have a long experience in developing and maintaining open-source tooling for OCaml, such as Opam,TryOCaml, ocp-indent, ocp-index, and ocp-browser, and we contribute to the core-development of OCaml, notably with our work on the Flambda optimizer branch. Another area of expertise is that of Formal Methods, with tools such as our SMT Solver Alt-Ergo (check ourAlt-Ergo Users’ Club). We also provide vocational trainings in OCaml and Rust, and we can build courses on formal methods on-demand. Do not hesitate to reach out by email:contact@ocamlpro.com.
以上所述就是小编给大家介绍的《opam 2.1.0 alpha is here!》,希望对大家有所帮助,如果大家有任何疑问请给我留言,小编会及时回复大家的。在此也非常感谢大家对 码农网 的支持!
猜你喜欢:本站部分资源来源于网络,本站转载出于传递更多信息之目的,版权归原作者或者来源机构所有,如转载稿涉及版权问题,请联系我们。
爱上Arduino
Massimo Banzi / 于欣龙、郭浩赟 / 人民邮电出版社 / 2012-10 / 38.00元
《硬件开源电子设计平台:爱上Arduino(第2版)》全面透彻地介绍了arduino的相关内容,它会给你带来许多项目的点子,并帮助你顺利地实现从开始策划直到完成安装的全过程。由于《硬件开源电子设计平台:爱上Arduino(第2版)》是arduino项目合作创始人massimobanzi所著,其中一定融入了创始人对开源硬件的独到见解。《硬件开源电子设计平台:爱上Arduino(第2版)》内容完全考虑......一起来看看 《爱上Arduino》 这本书的介绍吧!