From: "Nicolás Ojeda Bär" <nicolas.ojeda.bar@lexifi.com>
To: Martin DeMello <martindemello@gmail.com>
Cc: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] how do you develop multiple dependent projects simultaneously?
Date: Mon, 31 Jul 2017 22:41:15 +0200 [thread overview]
Message-ID: <CADK7aFPJrXvc0JK42-VE0bwOuUWc2k5huE6Q+httscVPugirHQ@mail.gmail.com> (raw)
In-Reply-To: <CAFrFfuEnbmtvd3gXEfA+77SSyW5x4ekxTYnGjUpXpepY1y1krA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1104 bytes --]
Hi Martin,
Other people will be able to give you a more extensive answer, but my
understanding is that jbuilder supports this workflow directly.
So if your project and both libraries use jbuilder you can just drop both
local git repos somewhere in your tree and everything will work
automatically.
See
http://jbuilder.readthedocs.io/en/latest/project-layout-specification.html
for the details.
Best wishes,
Nicolas
On Mon, Jul 31, 2017 at 10:33 PM, Martin DeMello <martindemello@gmail.com>
wrote:
> I have a project that depends on two other libraries, both pinned to
> local git repos in opam. However I find it quite annoying to have to
> run opam update && opam install every time I make a change in the
> libraries, especially when I'm making small changes to all three
> projects at the same time. Is there any smoother workflow that people
> use?
>
> martin
>
> --
> Caml-list mailing list. Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
[-- Attachment #2: Type: text/html, Size: 1997 bytes --]
next prev parent reply other threads:[~2017-07-31 20:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-31 20:33 Martin DeMello
2017-07-31 20:41 ` Nicolás Ojeda Bär [this message]
2017-07-31 20:43 ` David Allsopp
2017-08-01 9:19 ` Gerd Stolpmann
2017-08-03 11:52 ` rixed
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=CADK7aFPJrXvc0JK42-VE0bwOuUWc2k5huE6Q+httscVPugirHQ@mail.gmail.com \
--to=nicolas.ojeda.bar@lexifi.com \
--cc=caml-list@inria.fr \
--cc=martindemello@gmail.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