Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Matej Kosik <5764c029b688c1c0d24a2e97cd764f@gmail.com>
To: caml-list@inria.fr
Subject: [Caml-list] Ubuntu + Batteries ... missing (?) Batteries_uni module
Date: Thu, 31 Oct 2013 19:06:03 +0000	[thread overview]
Message-ID: <5272AA1B.1040403@gmail.com> (raw)

Hi,

My colleague recently updated his Ubuntu box and, after upgrade, he noticed that he cannot compile my Ocaml programs, which rely on Batteries.

I looked into the matter and noticed a version mismatch

  libbatteries-ocaml-dev version 1.4.3-1 in Debian 8 (my machine)
  http://packages.debian.org/jessie/amd64/libbatteries-ocaml-dev/filelist

  libbatteries-ocaml-dev version 2.0-1 in Ubuntu 13 (his machine)
  http://packages.ubuntu.com/saucy/amd64/libbatteries-ocaml-dev/filelist

Compilation failure is related to the fact that

  Batteries_uni

module is not present.

  # This:
  #
  #   apt-file search batteries_uni.cmi
  #
  # does not return anything on Ubuntu 13 whereas on Debian 8 it returns:
  #
  #   libbatteries-ocaml-dev: /usr/lib/ocaml/batteries/batteries_uni.cmi

so he is getting:

  Error: Unbound module Batteries_uni

I understand that the versions of the library are different (1.4.3-1 vs 2.0-1) so the API can be incompatible,
although missing Batteries_uni module is surprising because it is not declared to be removed from the latest Batteries version:

  http://ocaml-batteries-team.github.io/batteries-included/hdoc/Batteries_uni.html

I would like to ask whether this situation is correct (and I should not rely on Batteries_uni module anymore) or it is a ommision (breakage) in Ubuntu package?

Thanks in advance for the help.

             reply	other threads:[~2013-10-31 19:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-31 19:06 Matej Kosik [this message]
2013-10-31 20:43 ` Jacques-Pascal Deplaix

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5272AA1B.1040403@gmail.com \
    --to=5764c029b688c1c0d24a2e97cd764f@gmail.com \
    --cc=caml-list@inria.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox