From: Anil Madhavapeddy <anil@recoil.org>
To: Kenneth Adam Miller <kennethadammiller@gmail.com>
Cc: caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] opam-installext (Was: Ocaml programmers interested in human-level AI)
Date: Sat, 10 Jan 2015 18:57:47 +0000 [thread overview]
Message-ID: <B595F75C-FED3-4445-BE0C-71391A654D8A@recoil.org> (raw)
In-Reply-To: <CAK7rcp9HeXz3Lbdy0to4Zxd+8TvCU81V-SZsS3EquPaDPM6wDg@mail.gmail.com>
On 10 Jan 2015, at 18:44, Kenneth Adam Miller <kennethadammiller@gmail.com> wrote:
>
> The only thing I think the ocaml environment is missing is a static check of the surrounding environment for the tools that will be used, for use in opam. That way, when stuff builds, you get told all the dependencies instead of doing iterations of finding each missing thing by hand.
There's an OPAM plugin that the automated tests use that you may be interested in trying out.
Install it with:
opam install opam-installext
Then, if you have `sudo` configured correct you can just do:
opam installext <pkg1> <pkg2> ...
It will query the `depexts` field for each package which contains OS-specific external dependencies.
It's still not particularly well integrated into OPAM as it's external, but full support is in the works so that a plugin won't be needed in future revisions of OPAM.
-anil
next prev parent reply other threads:[~2015-01-10 18:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-10 16:29 [Caml-list] Ocaml programmers interested in human-level AI Eray Ozkural
2015-01-10 18:13 ` Peter Zotov
2015-01-10 18:38 ` Eray Ozkural
2015-01-10 18:44 ` Kenneth Adam Miller
2015-01-10 18:57 ` Anil Madhavapeddy [this message]
2015-01-10 19:04 ` [Caml-list] opam-installext (Was: Ocaml programmers interested in human-level AI) Kenneth Adam Miller
2015-01-10 19:39 ` [Caml-list] Ocaml programmers interested in human-level AI Eray Ozkural
2015-01-10 23:33 ` Benjamin Greenman
2015-01-10 23:36 ` Kenneth Adam Miller
2015-01-12 20:28 ` Adrien Nader
2015-01-11 13:47 ` Eray Ozkural
2015-01-11 11:39 ` Gerd Stolpmann
2015-01-12 13:22 ` Ben Millwood
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=B595F75C-FED3-4445-BE0C-71391A654D8A@recoil.org \
--to=anil@recoil.org \
--cc=caml-list@inria.fr \
--cc=kennethadammiller@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).