opam-repository VS opam

To be completely fair, they also did the same thing on the Tezos side by including 4083 commits from the tezos/opam-repository repo, since this is just a fork of of the official ocaml/opam-repository repo.

I'm trying to add core but get the following error: info checking https://github.com/ocaml/opam-repository for updates... .... resolving esy packages @opam/utoperror: Unable to read file /Users/USER/.esy/opam-repository/repo: No such file or directory resolving @opam/utop@* esy: exiting due to errors above

<><> Version-specific details <><><><><><><><><><><><><><><><><><><><><><><> 🐫 version 1 repository default homepage: "http://gnu.org/software/emacs" bug-reports: "https://github.com/ocaml/opam-repository/issues" authors: "[email protected]" maintainer: "[email protected]" license: "GPL-1.0-or-later" flags: conf synopsis Virtual package to install the Emacs editor description This package will install a system emacs if invoked via opam depext ```

Would you care to open an issue on the opam-repository, or ideally send a Pull Request implementing the improvement?

I've managed to install opam (and OCaml) directly on an Xperia XA2 running Sailfish X using setarch (see also https://github.com/ocaml/opam-repository/issues/14804).

According to this github comment you need to disable sandboxing by "using the --disable-sandboxing option for opam init in a fresh opam initialisation or via an opamrc. For an initialised opam, you can't use this option, but change the configuration directly in the config file by removing / empty wrap-*-command fields."

Regarding toolchain managers, those developing software with Rust would use rustup, OCaml developers would use opam, Haskell GHCup, and Python with pyenv. Likwise, Rust already uses cargo for package management, Python can use pip and venv, cabal for Haskell, and opam still for OCaml.

The project has a planning board for 2.2 on https://github.com/ocaml/opam/projects/2 and there are many active PRs on the repo. I wouldn’t hazard an accurate ETA but it is being actively worked on right now.

nodc. (not opam, don't care)

Maybe you'll find this issue helpful (though I didn't): https://github.com/ocaml/opam/issues/3773

That being said, the experience on Windows could definitely be better. The bright side is that the community is aware of this and is making progress on improving it. If you're curious, you can take a look at some of the Windows-related plans for opam 2.2 (pdf).

With Dune, given the executable main, you would write the following dune file to use library mylib if it was published on Opam.

This is caused by bubblewrap requiring specific permissions when running in Docker containers. Disabling sandbox does make you install OCaml, but there is a risk of installation scripts of packages wiping home directory https://github.com/ocaml/opam/issues/3231