Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Louis Gesbert <louis.gesbert@ocamlpro.com>
To: caml-list@inria.fr, "Daniel Bünzli" <daniel.buenzli@erratique.ch>
Cc: "Christoph Höger" <christoph.hoeger@tu-berlin.de>
Subject: Re: [Caml-list] Passing configuration options to opam
Date: Tue, 06 Sep 2016 12:34:30 +0200	[thread overview]
Message-ID: <2170048.Zk88dHpl0p@agaric> (raw)
In-Reply-To: <3A394B73874C405CAC4515AD24757E9F@erratique.ch>

> - Daniel Bünzli, 06/09/2016 11:49 -
> On Tuesday 6 September 2016 at 11:46, Daniel Bünzli wrote:
> > You can do `opam pin edit ocaml-lua` and change the build instructions to your wishes. But best would be to upstream luajit discovery.
> 
> Note that you will first need to pin to a specific version using e.g. `opam pin add ocaml-lua 1.4`

[not anymore in opam 2.0, but it's not out yet]

  reply	other threads:[~2016-09-06 10:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-06  9:25 Christoph Höger
2016-09-06  9:46 ` Daniel Bünzli
2016-09-06  9:49   ` Daniel Bünzli
2016-09-06 10:34     ` Louis Gesbert [this message]
2016-09-06 11:47       ` Ivan Gotovchits

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=2170048.Zk88dHpl0p@agaric \
    --to=louis.gesbert@ocamlpro.com \
    --cc=caml-list@inria.fr \
    --cc=christoph.hoeger@tu-berlin.de \
    --cc=daniel.buenzli@erratique.ch \
    /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