[opam-devel] Travis CI failures
agarwal1975 at gmail.com
Tue Sep 30 22:06:19 BST 2014
Going from nothing to a working OCaml installation is still a little too
hard, but only in terms of knowing what to do. Everything works if you know
what commands to run in all the various scenarios. In other words, the
Install page needs a lot more love.
On Tue, Sep 30, 2014 at 4:39 PM, Anil Madhavapeddy <anil at recoil.org> wrote:
> Ashish, this is *very* useful as it's the first stumbling block that users
> run into and give up when they do. Thank you!
> On 30 Sep 2014, at 17:16, Ashish Agarwal <agarwal1975 at gmail.com> wrote:
> Thanks for the explanations. I spent all day learning more about package
> management on several OS's, and updated the ocaml.org install page.
> Hopefully things are a bit clearer.
> On Tue, Sep 30, 2014 at 4:27 AM, Anil Madhavapeddy <anil at recoil.org>
>> On 29 Sep 2014, at 19:46, Ashish Agarwal <agarwal1975 at gmail.com> wrote:
>> 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.
>> 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
>> I still don't know what to do on CentOS to get ocamldoc. Does anyone have
>> the full list of packages for each OS?
>> 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
>> 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.
>> 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.
>> 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..
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the opam-devel