Overview
Request 579328 superseded
Multi Criteria CUDF Solver with OCaml bindings.
It is a dependency of jbuilder, which is used for building some dependencies of the next version of Haxe (v4.0.0).
This supersedes the previous request for updated build dependency and new upstream version.
- Created by onthewings
- In state superseded
- Supersedes 570831
- Superseded by 582459
- Open review for openSUSE:Factory:Staging:adi:69
Still, I don't understand why this is sent to Factory as opam is not… opam 2.0 is not ready yet.
I will submit opam to Factory as well, it is just I'm doing it in a smaller batch at a time in case there is something to adjust in individual package.
I'm not oppose to shipping opam 1.2.2 instead. FYI, Fedora and pkgsrc already ships opam 2.
opam 1.2.2? Yeah, of course, feel free to package it yourself.
Please note: - I packaged ocaml-mccs that you want to push to Factory + opam - I don't want to maintain them for Factory yet - So if you want them now in Factory, you better step up to maintain them instead of pushing things without even asking
Besides, I don't know your Haxe stuff but right now it looks strange to me that opam is a dependency of anything.
And @olh, if you're accepting such a request, I consider you'll maintain the package yourself too.
I thought submitting an request to Factory directly would be simpler since maintainers would be notified as well. I'm sorry if it doesn't sound polite.
I'm happy to maintain opam, 1.2.2 or 2.0. But I'm not sure how to handle 1.2.2 since opam in devel:languages:ocaml is already at 2, downgrading it or creating separate package doesn't seem right.
opam's "opam-installer" command line tool is used by jbuilder (now dune) when calling jbuilder install .... Thus it is a build dependency of the OCaml libraries that use jbuilder.
I think in the end this will create circular dependencies. The chain should be C-Compiler - ocaml - jbuilder - other_pkgs at some point. In other words, jbuilder should do the install, not opam.
You won't downgrade existing opam package to 1.x, you can create another package if you want (though I'm not sure it's relevant).
As olh said, you better think about the circular dependencies before. As far as I know we don't use 'jbuilder install' to install files yet.
I packaged devel:languages:ocaml/ocaml-migrate-parsetree recently and it used jbuilder install in its Makefile. Is there any problem with this?
As long as ocaml-migrate-parsetree is not a build dependency of opam, there is no problem. ocaml-mccs for example is a dependency of opam so we don't use jbuilder install here.
Well actually, if the library is not a dependency of opam itself it shouldn't bring circular dependencies.
Request History
onthewings created request
Multi Criteria CUDF Solver with OCaml bindings.
It is a dependency of jbuilder, which is used for building some dependencies of the next version of Haxe (v4.0.0).
This supersedes the previous request for updated build dependency and new upstream version.
licensedigger accepted review
ok
staging-bot added as a reviewer
Being evaluated by staging project "openSUSE:Factory:Staging:adi:69"
staging-bot accepted review
Picked openSUSE:Factory:Staging:adi:69
factory-auto added opensuse-review-team as a reviewer
Please review sources
factory-auto added repo-checker as a reviewer
Please review build success
factory-auto accepted review
Check script succeeded
repo-checker accepted review
cycle and install check passed
dimstar declined review
Please package LICENSE files as %license, not as %doc
dimstar declined request
Please package LICENSE files as %license, not as %doc
Multi Criteria CUDF Solver with OCaml bindings.
It is a dependency of jbuilder, which is used for building some dependencies of the next version of Haxe (v4.0.0).
Update: Package LICENSE files as %license.
