Re: Bug#599215: Homonymous modules that will conflict in META makes dh-ocaml choke.
Le 06/10/2010 20:32, Guillaume Yziquel a écrit :
You would have a hierarchy of folders like /usr/lib/ocaml/python/X.X/*
How do you plan to handle reverse dependencies?
There is a similar issue with llvm, but it doesn't use dh_ocaml. I'm not
sure at the moment of what would be the proper way to dh_ocaml-enable it.
I would not like to be able to rename the oCamlPython files upstream
(although I will
presumably be forced to). Keep in mind that they cannot be loaded
simultaneously because
of the META file conflict. The problem is that dh-ocaml fails with
dh_ocaml -s
E: Error: unit OCamlPython exported in libpython3.2-ocaml-dev v0.90-2
but already exported by libpython-ocaml-dev v0.90-1
E: Error running /usr/bin/ocaml-md5sums --md5sums-dir
debian/libpython3.2-ocaml-dev//var/lib/ocaml/md5sums --md5sums-dir
debian/libpython2.5-ocaml-dev//var/lib/ocaml/md5sums --md5sums-dir
debian/libpython2.6-ocaml-dev//var/lib/ocaml/md5sums --md5sums-dir
debian/libpython3.1-ocaml-dev//var/lib/ocaml/md5sums --md5sums-dir
debian/libpython2.7-ocaml-dev//var/lib/ocaml/md5sums --md5sums-dir
debian/libpython2.4-ocaml-dev//var/lib/ocaml/md5sums --load-info
debian/libpython3.2-ocaml-dev.oinfo.debhelper dep at /usr/bin/dh_ocaml
line 448.
make: *** [common-binary-predeb-arch] Erreur 255
dpkg-buildpackage: erreur: fakeroot debian/rules binary a produit une
erreur de sortie de type 2
What kind of dependency would you expect for something that depends on
your bindings?
I do not understand exactly the question. For now I'd appreciate being
able to do something like:
ocamlfind ocamlc -package python26.interpreter pythonmodulebinding.ml
Does that answer your question?
No.
Which package would provide the META file?
Cheers,
--
Stéphane
Reply to: