From: rixed@happyleptic.org
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: Thu, 3 Aug 2017 13:52:27 +0200 [thread overview]
Message-ID: <20170803115227.alhxizymgjaybdct@captain.the-shell.happyleptic.org> (raw)
In-Reply-To: <CAFrFfuEnbmtvd3gXEfA+77SSyW5x4ekxTYnGjUpXpepY1y1krA@mail.gmail.com>
-[ Mon, Jul 31, 2017 at 01:33:45PM -0700, Martin DeMello ]----
> 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?
You do not have to; "opam upgrade $name_of_the_lib" is all that should
be required. that's how I work and it's ok, but I do not change those
lib very often anyway.
prev parent reply other threads:[~2017-08-03 11:52 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
2017-07-31 20:43 ` David Allsopp
2017-08-01 9:19 ` Gerd Stolpmann
2017-08-03 11:52 ` rixed [this message]
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=20170803115227.alhxizymgjaybdct@captain.the-shell.happyleptic.org \
--to=rixed@happyleptic.org \
--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;
as well as URLs for NNTP newsgroup(s).