caml-list - the Caml user's mailing list
 help / Atom feed
From: Ian Zimmerman <>
Subject: Re: [Caml-list] opam and dune [Was: How to use -map]
Date: Thu, 14 Nov 2019 16:32:04 -0800
Message-ID: <> (raw)
In-Reply-To: <>

On 2019-08-08 08:38, Rudi Grinberg wrote:

> For now the .opam file needs to be in version control. It's not ideal that
> we need to check in generated files, so hopefully this problem will be
> addressed in opam. 

>! If this truely bothers you, you can always disable the opam file
>! generation and write your opam file manually.

How?  The manual doesn't say, as far as I can see.  In fact, it doesn't
say how to _enable_ it either, or that it is on by default.  The entire
subsection of the manual called "Generating opam files" consists of some
example syntax from a dune file.

This is why I have been resisting the dune wave: the doc too often loses
view of the forest.

Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
To reply privately _only_ on Usenet and on broken lists
which rewrite From, fetch the TXT record for

  parent reply index

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-31 21:18 [Caml-list] How to use -map , -no-alias-deps and friends? Ian Zimmerman
2019-07-31 21:52 ` Nicolás Ojeda Bär
2019-08-06 18:48   ` Ian Zimmerman
2019-08-07 20:32     ` [Caml-list] opam and dune [Was: How to use -map] Ian Zimmerman
2019-08-08  1:39       ` Rudi Grinberg
2019-08-08 17:48         ` Hendrik Boom
2019-08-08 17:54           ` Rudi Grinberg
2019-08-08 19:38             ` Daniel Bünzli
2019-11-15  0:32         ` Ian Zimmerman [this message]
2019-08-08 18:05       ` Yawar Amin
2019-08-08 19:03         ` Josh Berdine
2019-07-31 22:08 ` [Caml-list] How to use -map , -no-alias-deps and friends? Florian Angeletti
2019-07-31 23:15   ` Ian Zimmerman
2019-08-01  9:40     ` Florian Angeletti

Reply instructions:

You may reply publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

caml-list - the Caml user's mailing list

Archives are clonable: git clone --mirror

AGPL code for this site: git clone public-inbox