Alexander Bantyev
Alexander Bantyev
Ah, no, I think you misunderstood me? I'm proposing something like this: ```nix { outputs = { self, opam-nix, nixpkgs }: { legacyPackages.x86_64-linux = opam-nix.lib.x86_64-linux.buildOpamProject { } ./. { #...
FYI, I have changed the interface a bit: now `buildOpamProject` accepts a `name` and only builds one package from the project, and the old `buildOpamProject` is now `buildOpamProject'`
Drafted due to no progress being possible at the moment, particularly in light of @roberth 's comment and steering committee discussions.
`ocaml-base-compiler = "*"` just gets passed along to `opam` as `--packages ocaml-base-compiler`, which should select the latest version (to some definition of "latest"). I believe `5.0.0` is a release, and...
Not sure what else you are expecting? It seems to be behaving according to the documentation.
You might to be looking at the wrong version of opam-repository; mind that by default `opam-nix` uses the version pinned in flake.lock (at this point, it's 786c55fa77c37f07eceea7d6a9bec04d2225e302)
> Also, can just set criteria = null in resolveArgs to automatically get opam's default. Is the reason that criteria is specified in defaultResolveArgs just to improve the stability of...
Is this fixed by #110?
Closing under the assumption that this is fixed
Hi! Should be fixed now. If you encounter more problems, please feel free to open corresponding issues.