[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: State of ocamlgraph



Hello,

On Mon, Dec 20, 2021 at 08:34:34AM +0100, Stéphane Glondu wrote:
> Le 18/12/2021 à 22:17, Ralf Treinen a écrit :
> >>> I've noticed with my opam monitoring [1] that ocamlgraph is not
> >>> up-to-date in Debian unstable compared to opam (1.8.8 instead of 2.0.0).
> >>> I've seen you've uploaded version 2.0.0 to experimental; are you
> >>> planning to upload it to unstable? When?
> >>
> >> I think one of the reasons why I uploaded only to experimental is that
> >> it was already quite close to the freeze. I think there were also some
> >> packages that didn't compile with ocamlgraph 2.0.0, but I do not
> >> remember which ones. It seems that at least alt-ergo,ben,frama-c,why3.
> 
> Ben is Debian-specific and probably can be adapted easily if needed.

ben compiles fine with ocamlgraph 2.0.0.

> > In fact since the passage to dune, ocamlgraph does no longer produce
> > graph.cmo (https://github.com/backtracking/ocamlgraph/issues/118),
> > which is a problem at least for why3, unless we decide to give up on
> > bytecode since apparently everybody else already has.
> 
> I does produce graph.cma and graph.cmi.

In fact the why3 upstream git has already a patch for this. I'll just have
to fight a bit with dh_ocaml --no-defined-map.

So I'll upload ocamlgraph right away.

-Ralf.


Reply to: