From: Jeremie Dimino <jdimino@janestreet.com>
To: "francois.pottier@inria.fr" <francois.pottier@inria.fr>,
caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] (dune/opam) Proper way of vendoring a library inside an application?
Date: Mon, 3 Feb 2020 14:16:52 +0000 [thread overview]
Message-ID: <CANhEzE6g9z-ipXhH4qEtTJF1-7AJYJ9HX=XTVX=QykPOQ7bsOA@mail.gmail.com> (raw)
In-Reply-To: <CANhEzE6LX7Vz_Nzj5zq2c0s+qN-bWOx88QG=mpRExnehmGak+w@mail.gmail.com>
Here are the PR fixing these:
https://github.com/ocaml/dune/pull/3074
https://github.com/ocaml/dune/pull/3075
On Mon, Feb 3, 2020 at 10:26 AM Jeremie Dimino <jdimino@janestreet.com> wrote:
>
> Hi François,
>
> On Fri, Jan 31, 2020 at 8:48 AM François Pottier
> <francois.pottier@inria.fr> wrote:
> > * "dune install" installs Menhir *and Fix*, though I would like
> > it to install Menhir only.
> >
> > * Attempting to pin Menhir using "opam pin" fails because opam
> > cannot find Fix (inded, Fix is not globally installed).
>
> These look like bugs in Dune, we'll fix them for the next release.
>
> Cheers,
>
> Jeremie
--
Jeremie
next prev parent reply other threads:[~2020-02-03 14:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-31 8:48 François Pottier
2020-01-31 13:08 ` François Bobot
2020-01-31 14:53 ` François Pottier
2020-02-03 10:26 ` Jeremie Dimino
2020-02-03 14:16 ` Jeremie Dimino [this message]
2020-02-03 14:53 ` François Pottier
2020-02-03 23:13 ` Jeremie Dimino
2020-02-04 9:10 ` François Pottier
2020-02-06 22:33 ` Jeremie Dimino
2020-02-10 9:37 ` [Caml-list] dune for OCaml < 4.07? François Pottier
2020-02-10 10:18 ` David Allsopp
2020-02-10 10:33 ` François Pottier
2020-02-10 11:27 ` David Allsopp
2020-02-29 8:41 ` [Caml-list] (dune/opam) Proper way of vendoring a library inside an application? Richard W.M. Jones
2020-02-29 11:20 ` François Pottier
2020-03-02 9:33 ` François Bobot
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='CANhEzE6g9z-ipXhH4qEtTJF1-7AJYJ9HX=XTVX=QykPOQ7bsOA@mail.gmail.com' \
--to=jdimino@janestreet.com \
--cc=caml-list@inria.fr \
--cc=francois.pottier@inria.fr \
/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).