Stefano Zacchiroli <zack@debian.org> (10/09/2007):
> You should create 2 packages: "libgv-ocaml" should contain only the
> .so, but should ship it under /usr/lib/ocaml/3.10/stublibs/; the other
> (a new one) "libgv-ocaml-dev" should contain the compiled version of
> gv.ml{,i} and ship it under /usr/lib/ocaml/3.10/graphviz/. More
> details on how to do that can be found in the policy.
OK, I wasn't sure how the policy applies to this particular case (and
I've still have to read it more thoroughly). I'm wondering whether
putting the (OCaml) -dev part into the libgraphvizN-dev package would be
acceptable, so as to limit the number of binary packages I'm building
from a single source package.
> If you are maintaining graphviz collaboratively on some repository I
> guess we can find some of us willing to do the work directly on the
> graphviz package. Just let us know.
You can find the git tree on git.debian.org, any patch is very welcome.
(And I'm also back on #debian-ocaml, now that my bouncer's back.)
Thanks for your help.
Cheers,
--
Cyril Brulebois
Attachment:
pgp_o9CQqBKwz.pgp
Description: PGP signature