From: Fabrice Le Fessant <Fabrice.Le_fessant@inria.fr>
To: "François Bobot" <francois.bobot@cea.fr>
Cc: Ocaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] [ANN] drom.0.2.0: OCaml Project Manager, beta release
Date: Wed, 25 Nov 2020 22:10:57 +0100 [thread overview]
Message-ID: <CAHvkLrNFXhGzUeJTjNbWZF1NFfKRweo4C3-uSJCMSHYeN-duSA@mail.gmail.com> (raw)
In-Reply-To: <86e52b14-1176-e774-289e-dcf5a6788b06@cea.fr>
Hi François,
On Wed, Nov 25, 2020 at 2:22 PM François Bobot <francois.bobot@cea.fr> wrote:
> I'm very happy to see work in the OCaml world in that direction. I was currently looking for
> duniverse for that kind of need. Do they fullfil different needs or how do they compare?
My understanding is that `duniverse` tackles the problem of the
"mono-repo", i.e. when you want to manage many different projects as
just one project, using `dune` capacity to build them all at once. I
would say that `drom` tackles an orthogonal problem, which is to
simplify the creation of simple OCaml projects (generating all the
standard files you need, like Makefile, dune-project, dune,
.ocamlformat, .github CI, documentation, license, etc.) and day-to-day
management (changing dependencies, having a copy of headers that you
can insert in new files, etc.). It also provides a single interface
over basic opam/dune commands.
It would probably be possible to use `duninverse` on a set of projects
containing projects generated by `dune`, but I don't know enough about
`duniverse` to be sure.
Of course, `drom` can manage projects composed of multiple libraries
and executables (called `packages` because `drom` generates one `opam`
file for every one of them), but I wouldn't call that a mono-repo,
it's just frequent to have more than one package in a small project.
--
Fabrice
prev parent reply other threads:[~2020-11-25 21:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 13:05 Fabrice Le Fessant
2020-11-25 13:21 ` François Bobot
2020-11-25 21:10 ` Fabrice Le Fessant [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=CAHvkLrNFXhGzUeJTjNbWZF1NFfKRweo4C3-uSJCMSHYeN-duSA@mail.gmail.com \
--to=fabrice.le_fessant@inria.fr \
--cc=caml-list@inria.fr \
--cc=francois.bobot@cea.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