Package: libcore-ocaml-dev
Version: 0.6.0-2+3.12.0+1
Severity: minor

META file doesn't specify that core should be used only with threads. There is 
indeed a dependency on threads in the following declaration in the META file:

requires = "bigarray, unix, res, sexplib, bin_prot, threads, fieldslib"

But the 'archive' statements should probably require the 'mt' tag. And throwing 
an error in the absence of threads.

However, this is a subotpimal situation, as there are many declarations and 
interfaces that one would wish to use even in the absence of threads. A much 
better situation would be to have a non-multithreaded version of core, that 
would, for example, not include the Timer module (that requires the Condition 
module and hence threads). Not sure however if this is a Debian issue or an 
upstream issue.

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (900, 'testing'), (700, 'stable'), (500, 'stable'), (90, 
'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_CH.UTF-8, LC_CTYPE=fr_CH.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages libcore-ocaml-dev depends on:
ii  libbin-prot-camlp4-dev 1.2.23-1+3.12.0+1 type-safe binary serialization for
ii  libcore-ocaml [libcore 0.6.0-2+3.12.0+1  Jane Street's standard library for
ii  libfields-camlp4-dev [ 0.1.0-2+3.12.0+1  OCaml syntax extension that enable
ii  libres-ocaml-dev [libr 3.2.0-2+3.12.0+1  OCaml library for automatically re
ii  libsexplib-camlp4-dev  4.2.16-1+3.12.0+1 automated conversions between OCam
ii  ocaml-findlib          1.2.5+debian-2~1  management tool for OCaml librarie
ii  ocaml-nox [ocaml-nox-3 3.12.0-1~38       ML implementation with a class-bas

Versions of packages libcore-ocaml-dev recommends:
ii  libcore-ocaml-doc       0.6.0-2+3.12.0+1 Jane Street's standard library for

libcore-ocaml-dev suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to