From: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
To: Nick Chapman <nchapman@janestreet.com>
Cc: Alain Frisch <alain.frisch@lexifi.com>,
OCaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] ocamldep, transitive dependencies, build systems, flambda
Date: Tue, 19 Jul 2016 11:46:41 +0200 [thread overview]
Message-ID: <26A20AD7AE4E496E800C8505AA376189@erratique.ch> (raw)
In-Reply-To: <CANViCaQozEoDvXf4NcOt-xr3dgjWZfujBWX6zZXh5H3ExejWtg@mail.gmail.com>
Le mardi, 5 juillet 2016 à 11:17, Nick Chapman a écrit :
> There was a further issue we needed to solve to get our scheme working. Suppose library A lists library B as a dependency and allows this dependence to be exposed in its interface. Clients of library A will require access to the .cmi's of library B to be compiled but it seems unreasonable to require them to explicitly list library B as a dependency. We solve this by automatically running ocamlinfo on the public .cmi's of a library to discover additional library deps required by clients of the library.
I think this is the best way of having underspecified dependencies. Suppose the client starts using B aswell, it won't have anything to specify since A is using it. Now suppose that for some reason A stops using B, suddenly your package will no longer compile because it's missing a dependency towards B.
Best,
Daniel
next prev parent reply other threads:[~2016-07-19 9:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-04 16:49 Alain Frisch
2016-07-05 9:17 ` Nick Chapman
2016-07-18 14:47 ` Alain Frisch
2016-07-19 9:20 ` Goswin von Brederlow
2016-07-19 9:46 ` Daniel Bünzli [this message]
2016-07-05 12:00 ` François Bobot
2016-07-05 13:53 ` Gerd Stolpmann
2016-07-05 13:06 Hongbo Zhang (BLOOMBERG/ 731 LEX)
2016-07-05 13:17 ` Gabriel Scherer
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=26A20AD7AE4E496E800C8505AA376189@erratique.ch \
--to=daniel.buenzli@erratique.ch \
--cc=alain.frisch@lexifi.com \
--cc=caml-list@inria.fr \
--cc=nchapman@janestreet.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).