[opam-devel] Start of an opam multi-architecture proposal

Daniel Bünzli daniel.buenzli at erratique.ch
Tue Oct 13 12:04:51 BST 2015

Le mardi, 13 octobre 2015 à 11:23, Thomas Gazagnaire a écrit :
> but the constraint "all installed packages should be installed on all architectures" is too strong.  

Note that the simplicity of the proposal strongly relies on this. It means that the notion of package installation in a switch is kept exactly the same as it is now — and hence is the same whether you use cross or not. This means that we don't need to introduce new concepts and bureaucracy to be able to talk about a notion of partial installation in a switch and a lot of things remains identical to what it is now, e.g the display of opam info, etc.  

Le mardi, 13 octobre 2015 à 11:46, Daniel Bünzli a écrit :
> If you don't do this then you need to be able to introduce architecture specifiers in variables (e.g. PKG:$(ARCH):installed) which I think we should avoid.
However we will still need something along the line of `pkg config var —arch` since package configuration variables [1] should be arch specific. If you use them in the build instructions of an opam file they would direct you directly to the ones for you arch, but if you use them from "outside" opam, e.g. on the cli, you have to specify which arch you are talking about.


[1] https://github.com/ocaml/opam/issues/2247

More information about the opam-devel mailing list