cuite VS opam-repository

Some extra notes: - nix is useful to install binary packages, since the default package repository is limited - I got both https://github.com/let-def/cuite and https://github.com/Kakadu/lablqml working for writing GUI apps. lablqml even uses the Sailfish-specific styling

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