opam-cross-* are seriously lagging behind the official opam repository and fdopen’s opam-windows, not least because importing packages by hand is a lot of work. I suppose at least a semi-automated process could help those repos grow and stay in sync with the upstream much faster. I’ve made a proto…

That’s a great initiative! Here are a couple of thoughts: For dune-based packages, things are indeed pretty straight-forward. Finding out which dependencies need to be ported as cross-dependency is indeed the part that’s hard to automatize For other build systems, it’s less clear to me how to auto…

In my imagination, it will work like this: initial package import will be computer-aided but with a human in the leading role. However, subsequent updates can be made by robotic pull requests, since packages rarely make big changes to their dependencies. At the point when most packages from opam-re…

I’m not sure if I understand the premise of dependabot. Why would anyone hardcode specific dependency versions? Maybe it makes sense in certain ecosystems that suffer from never-ending ecological disasters… :wink: In any case, most opam packages don’t have a constraint on the upper versions of thei…

[image] dmbaturin: Why would anyone hardcode specific dependency versions? It’s common practice nowadays to use semantic versioning and have lockfiles for reproducible builds. Dependabot updates semantic version ranges and lockfiles. See e.g. Bump standard from 0.2.2 to 0.2.3 by dependabot-…

This is really nice! I was thinking about implementing a tool like this back when I started opam-cross-*, but the ecosystem didn’t seem quite ready for it, and I ended up pushing for cross-compilation support in ocamlfind, topkg, etc instead. I’m really happy to see that dune now allowss turnkey con…

I’m not sure if the ecosystem is completely ready for it now. I’m pretty sure if/when this takes off, many packages will need fixes to be friendly to unattended porting. Still, from my experience porting 20+ packages to opam-cross-windows (an experience I hope to never repeat, hence the tool), only…

The ecosystem is never completely ready for something until you drag it there, kicking and screaming; or, more often, tired and indifferent. Though that figure of speech is really overly dramatic here, I found that most people working on OCaml projects are happy to assist. In other words, the only …

[ANN] [prototype] Dismas: a tool for automatically making cross-versions of opam packages

Ecosystem

XVilka March 30, 2020, 3:16pm 4

For automated pull requests, you might be interested in Dependabot and OCaml

Topic		Replies	Views
Explorations on Package Management in Dune Community announce	31	3320	July 20, 2023
Extending Dune With Package Management Ecosystem	23	2442	April 30, 2020
Ocaml cross compiler? Ecosystem	8	5369	January 24, 2020
Opam-cross-windows now supports OCaml 4.14.0! Ecosystem opam , build , windows , cross-compilation , dune	0	840	July 11, 2022
Early work experimenting with zig as a cross-compiler for OCaml Ecosystem cross-compilation	17	2385	May 7, 2025

[ANN] [prototype] Dismas: a tool for automatically making cross-versions of opam packages

Related topics