From: "François Bobot" <francois.bobot@cea.fr>
To: caml-list@inria.fr
Subject: Re: [Caml-list] (dune/opam) Proper way of vendoring a library inside an application?
Date: Fri, 31 Jan 2020 14:08:06 +0100 [thread overview]
Message-ID: <73779f13-b8da-ca44-0f9e-b1e48ec846e4@cea.fr> (raw)
In-Reply-To: <f50f0acb-9e02-cc29-6da7-6e56f33f8b42@inria.fr>
Le 31/01/2020 à 09:48, François Pottier a écrit :
> I am trying to figure out how to "vendor" (embark) a private
> copy of a library inside a project. (Concretely, I would like
> to vendor Fix inside Menhir.) I want this fact to remain
> invisible, that is, installing Menhir should not result
> in installing or upgrading the user's public copy of Fix.
>
> I have copied the source tree for Fix inside the source tree
> for Menhir, and added a (vendored_dirs fix) stanza in Menhir's
> toplevel "dune" file.
> I am confused... what's the proper way of embarking a private
> library inside an application without installing it globally?
Will Fix be used for MenhirLib? It is just to understand the impact on users of the library.
Best,
--
François
next prev parent reply other threads:[~2020-01-31 13:08 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 [this message]
2020-01-31 14:53 ` François Pottier
2020-02-03 10:26 ` Jeremie Dimino
2020-02-03 14:16 ` Jeremie Dimino
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=73779f13-b8da-ca44-0f9e-b1e48ec846e4@cea.fr \
--to=francois.bobot@cea.fr \
--cc=caml-list@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