Issue 23 in ocaml-extlib: Conflict with Camomile

[codesite...@google.com]

Status: New
Owner: ----

New issue 23 by gildor...@gmail.com: Conflict with Camomile
http://code.google.com/p/ocaml-extlib/issues/detail?id=23

What steps will reproduce the problem?
1. Install camomile 0.8.X
2. Install extlib
3. Install any software that has transitive depends on extlib and camomile
(e.g. pgocaml + sqlexpr).

What is the expected output? What do you see instead?

The files /usr/lib/ocaml/camomile/camomile.cma
and /usr/lib/ocaml/extlib/extLib.cma
disagree over interface UChar

What version of the product are you using? On what operating system?

1.5.2/Debian unstable

Please provide any additional information below.

For more info see
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670474

[codesite...@google.com]

Updates:
Status: Accepted
Owner: ygrekheretix
Labels: Type-Enhancement Milestone-Release1.6 Priority-High

Comment #1 on issue 23 by ygrekheretix: Conflict with Camomile
http://code.google.com/p/ocaml-extlib/issues/detail?id=23

Proposed solution - build another cma without UChar and UTF8 modules and
provide it via subpackage so that interested parties can link against it..

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[codesite...@google.com]

Comment #2 on issue 23 by gildor...@gmail.com: Conflict with Camomile
http://code.google.com/p/ocaml-extlib/issues/detail?id=23

It won't work because uChar.cmi will be present in both directories and
program that compiled with the top package (not the subpackage) will not be
able to choose between extlib/uChar.cmi and camomile/uChar.cmi.

If I follow your idea, the only solution is to put uChar.cmi in a
sub-directory of extlib/ (e.g. extlib/foo/) or in a totally different
package (e.g. extlib-unicode/uChar.cmi).

[codesite...@google.com]

Comment #3 on issue 23 by ygrekheretix: Conflict with Camomile
http://code.google.com/p/ocaml-extlib/issues/detail?id=23

Thanks for the feedback! Indeed, you are correct. I guess it is not
possible to have subdirectories with ocamlfind, so the only solution left
is to provide two packages. Not _that_ bad..

[codesite...@google.com]

Updates:
Status: Started

Comment #4 on issue 23 by ygrekheretix: Conflict with Camomile
http://code.google.com/p/ocaml-extlib/issues/detail?id=23

With the next release extlib is going to provide and install by default two
ocamlfind packages : extlib (full, same as current) and extlib_min (without
UChar UTF8 Unzip Base64 modules) in order to mitigate this issue.

[codesite...@google.com]

Updates:
Status: Fixed

Comment #5 on issue 23 by ygrekheretix: Conflict with Camomile
http://code.google.com/p/ocaml-extlib/issues/detail?id=23

This issue was closed by revision r428.

[codesite...@google.com]

Updates:
Status: Started

Comment #6 on issue 23 by ygrekheretix: Conflict with Camomile
http://code.google.com/p/ocaml-extlib/issues/detail?id=23

Now I think of an alternative way to solve this. Clearly we want everybody
to upgrade extlib without UChar and UTF8, but without breaking any code.
Current solution requires everybody to change used package name from extlib
to extlib_min and it will causes chaos wrt dependencies. The proposed
solution is to build by default full cma with all modules, but have a
configure-time option to build cma without UTF8. This will allow to to
gradually introduce reduced set of modules on codebases that don't need it
(e.g. opam, debian, etc).

[codesite...@google.com]

Updates:
Status: Fixed

Comment #7 on issue 23 by ygrekheretix: Conflict with Camomile
http://code.google.com/p/ocaml-extlib/issues/detail?id=23

(No comment was entered for this change.)