Le 05/10/2010 20:26, Guillaume Yziquel a écrit :
However, there will be, in each of these libpythonX.X-ocaml-dev packages, an oCamlPython.cm[xo] binary/bytecode, without the oCamlPython.cmi file. This is to be able to load statically the interpreter. Much like the lablgtk.init findlib package.
Where would the oCamlPython.cmi file be? Are all these *.cm[xoi] files binary compatible?
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?
Cheers, -- Stéphane