From: Christian Lindig <christian.lindig@citrix.com>
To: Elliott Mitchell <ehem+xen@m5p.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Cc: Ian Jackson <Ian.Jackson@citrix.com>,
Edwin Torok <edvin.torok@citrix.com>, "wl@xen.org" <wl@xen.org>,
"dave@recoil.org" <dave@recoil.org>
Subject: Re: [PATCH 2/2] tools/ocaml: Default to useful build output
Date: Mon, 20 Jul 2020 08:38:40 +0000 [thread overview]
Message-ID: <1595234320493.39632@citrix.com> (raw)
In-Reply-To: <20200718033242.GB88869@mattapan.m5p.com>
> Time for a bit of controversy.
OCaml outside Xen has moved to a different model of building based on dune which is fast, declarative and reliable. The OCaml xenstore is stagnating because nobody with OCaml experience wants to touch it anymore. It would be beneficial for the health of the OCaml xenstore to split it out such that it could be worked on independently. You might argue that Make is still appropriate for building OCaml projects but the OCaml community has moved through several build systems, starting from Make, and learned the hard way that this is not an easy problem. After years of more-or-less successful build system the consensus is that dune is right one and it has resulted in combination with the Opam package manager the ecosystem to flourish. Alternatively, it would be possible to move OCaml xenstore to dune within the Xen tree but it would create a dependency on it.
-- C
next prev parent reply other threads:[~2020-07-20 8:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-18 3:32 [PATCH 2/2] tools/ocaml: Default to useful build output Elliott Mitchell
2020-07-20 8:25 ` Christian Lindig
2020-07-20 8:38 ` Christian Lindig [this message]
2020-07-20 9:00 ` Paul Durrant
2020-07-20 9:24 ` Christian Lindig
2020-07-20 9:36 ` Edwin Torok
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=1595234320493.39632@citrix.com \
--to=christian.lindig@citrix.com \
--cc=Ian.Jackson@citrix.com \
--cc=dave@recoil.org \
--cc=edvin.torok@citrix.com \
--cc=ehem+xen@m5p.com \
--cc=wl@xen.org \
--cc=xen-devel@lists.xen.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.