caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Rudi Grinberg <rudi.grinberg@gmail.com>
To: caml-list@inria.fr, Hendrik Boom <hendrik@topoi.pooq.com>
Subject: Re: [Caml-list] opam and dune [Was: How to use -map]
Date: Fri, 9 Aug 2019 00:53:53 +0700	[thread overview]
Message-ID: <15d7e631-8a0b-41fe-9792-9afaa8a8af93@Spark> (raw)
In-Reply-To: <20190808174802.7ticjmzgcgvjxvlc@topoi.pooq.com>

[-- Attachment #1: Type: text/plain, Size: 458 bytes --]

> Is this a bootstrapping issue? If so, having a generated file in
> version control is likely an inevitability.

The issue could be avoided if we could teach opam that some .opam files are generated. For example, opam could ask dune to build all .opam files with $ dune builld @opam. If we wanted something more build system agnostic, we could also just check-in a list of all package file names. Opam could then ask the $build-system to build all of them.

[-- Attachment #2: Type: text/html, Size: 775 bytes --]

  reply	other threads:[~2019-08-08 17:54 UTC|newest]

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:47   ` Ian Zimmerman
2019-08-07 20:32     ` [Caml-list] opam and dune [Was: How to use -map] Ian Zimmerman
2019-08-08  1:38       ` Rudi Grinberg
2019-08-08 17:48         ` Hendrik Boom
2019-08-08 17:53           ` Rudi Grinberg [this message]
2019-08-08 19:38             ` Daniel Bünzli
2019-11-15  0:32         ` Ian Zimmerman
2019-08-08 18:05       ` Yawar Amin
2019-08-08 19:03         ` Josh Berdine
2019-07-31 22:07 ` [Caml-list] How to use -map , -no-alias-deps and friends? Florian Angeletti
2019-07-31 23:14   ` Ian Zimmerman
2019-08-01  9:40     ` Florian Angeletti

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=15d7e631-8a0b-41fe-9792-9afaa8a8af93@Spark \
    --to=rudi.grinberg@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=hendrik@topoi.pooq.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).