On 2018-09-09 10:44, Ralf Jung wrote:
Hi Mehdi,
On 2018-09-07 12:42, Ralf Jung wrote:
Package: opam
Version: 2.0.0-2
Severity: normal
Dear Maintainer,
Quoting from https://opam.ocaml.org/doc/2.0/External_solvers.html:
As of 2.0.0, opam comes with a CUDF solver built-in by default, so
unless you
have specifically compiled without it, you shouldn't have to be
worried about
installing an external solver.
So, aspcud should at best be a recommendation, not a dependency.
Likely, it
should just be a suggestions; the internal solver is used by default
even when
aspcud is installed.
If I am not mistaken, the built-in solver is not enabled in the Debian
package
because we are missing ocaml-mccs to make it work. So, for now, the
dependency
is still needed.
Oh... that's a bummer, because using the new built-in solver is one of
the
biggest reasons to update to opam 2 for me. :/ aspcud keeps computing
really
strange solutions in some cases I frequently run into.
Indeed.
This also means Debian users will not get the default and
upstream-intended
behavior of opam, which will be very confusing in particular for
bugreports.
We agree. Our intent is to package ocaml-mccs in time to include it in
Buster and
have a full featured OPAM 2 in Debian. Unfortunately, we did not
anticpated ocaml-mccs's
packaging. But hopefully it is only a matter of time.
Is there an issue that tracks fixing this?
Not yet, (I didn't see an RFP or ITP bugreport about this) [1]. Do you
mind filing
an RFP bug please for ocaml-mccs? (and add
debian-ocaml-maint%40lists.debian.org in
the X-debbugs-CC).
[1] https://www.debian.org/devel/wnpp/
--
Mehdi
