opam-repository VS dune

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."

If you are using the dune build system, add the tag(s) to your dune-project file's package stanza. E.g.:

One way to get around this is to modify the api/dune file with (include_subdirs qualified); this means that every subdirectory of api/ can be referenced by module namespacing and we don't have to write dune files for every route (or pages) folder. However, the OCaml LSP does not like it and red squiggles will show up in the editor (although the app with still compile without errors). Trying to develop the app knowing those red squiggles cannot be vanquished would drive me nuts, so instead of using (include_subdirs qualified) I just wrote dune files for every route (and page) which gets rid of the red squiggles.

2) Neither would having all source/targets specified, as that would entail listing them all in the dune file as wildcard rules is apparently still not a thing: https://github.com/ocaml/dune/issues/307

There is a small example on the dune home page: https://dune.build/

Dune (https://dune.build/) is the preeminent build tool for OCaml development. I don't love its input syntax (s-expressions), and I sometimes miss the ability to write high-level functions to reduce boilerplate (especially for unit tests), but it always gets the dependencies right, and it's fast. This is in stark contrast to some of my experiences with various other build systems, and I am super happy that the default option for OCaml build systems is so good.

It's still weird because dune's own site only makes Jane Street references: https://dune.build/.

ONE of the big benefits of OCaml is its powerful REPL (also called the toplevel), the interactive command-line utility where you can load modules, type in and execute code, and see its results. The modern REPL, utop, has powerful auto-completion and integration with the build system dune, which enables productive workflows like loading an entire project's libraries in the REPL and interactively exploring them.