From: Simon Cruanes <simon.cruanes.2007@m4x.org>
To: Helmut Brandl <helmut.brandl@gmx.net>
Cc: caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] Opam packages and CI
Date: Tue, 9 Apr 2019 13:49:53 -0500 [thread overview]
Message-ID: <20190409184953.GL32706@church> (raw)
In-Reply-To: <75C9EEF2-FE3C-409C-AF3E-786CD5592F86@gmx.net>
[-- Attachment #1: Type: text/plain, Size: 470 bytes --]
I've had good experiences with travis recently, using the docker script
(an example here:
https://github.com/c-cube/iter/blob/master/.travis.yml).
if your package is opam 2-friendly it's just a matter of a local pin
and a few switches. there are other options (variables, really) to
install extra deps or deal with optional deps.
It's not particularly overkill since it just starts with a docker image
with pre-installed opam switches.
--
Simon Cruanes
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-04-09 18:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-09 18:14 Helmut Brandl
2019-04-09 18:49 ` Simon Cruanes [this message]
2019-04-09 18:54 ` Daniil Baturin
2019-04-09 21:36 ` Anil Madhavapeddy
2019-04-10 14:57 ` Helmut Brandl
2019-04-10 14:20 ` Louis Roché
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=20190409184953.GL32706@church \
--to=simon.cruanes.2007@m4x.org \
--cc=caml-list@inria.fr \
--cc=helmut.brandl@gmx.net \
/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).