<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">On 29 Sep 2014, at 19:46, Ashish Agarwal <<a href="mailto:agarwal1975@gmail.com">agarwal1975@gmail.com</a>> wrote:<br><div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">Thanks. I now have it working on Ubuntu. The issue is that several OS packages have to be installed, not just "ocaml" and "camlp4". Thus, the instructions [1,2] we've been linking people to are incomplete.</div></blockquote><div><br></div>That's right -- this has always been the case historically on Debian (somewhat suboptimally I think, but it fits in with their distribution criteria). I usually do "ocaml ocaml-native-compilers camlp4-extra" to get everything.</div><div><br><blockquote type="cite"><div dir="ltr"><div><br></div><div>I still don't know what to do on CentOS to get ocamldoc. Does anyone have the full list of packages for each OS?</div></div></blockquote><div><br></div>You should have got ocamldoc with just ocaml there. I believe you just need "ocaml" and "ocaml-camlp4" on CentOS, but please correct me if that's wrong. I don't regularly use it and so could have missed something in the packaging.</div><div><br><blockquote type="cite"><div dir="ltr"><div><br></div><div>Why are multiple packages needed? I would expect "apt-get install ocaml" or "yum install ocaml" to install everything that one gets from installing the source distribution of OCaml.<br><div><br></div><div>[1] <a href="http://software.opensuse.org/download.html?project=home:ocaml&package=opam">http://software.opensuse.org/download.html?project=home:ocaml&package=opam</a></div><div>[2] <a href="http://software.opensuse.org/download.html?project=home:ocaml&package=ocaml">http://software.opensuse.org/download.html?project=home:ocaml&package=ocaml</a></div></div></div></blockquote><div><br></div>That's just following upstream packaging practises. I think it's better to do that and to document what packages are needed, rather than changing it for our local efforts.</div><div><br></div><div>However, it could be easier. I'll take a look at making the Travis scripts a bit more automated by sourcing a central copy of the script from somewhere on GitHub. That'll reduce the rate of cut and pastes..</div><div><br></div><div>-anil</div><div><br></div></body></html>