Skip to Content.
Sympa Menu

coq-club - Re: [ocaml-platform] [Coq-Club] Coq opam package

coq-club AT inria.fr

Subject: The Coq mailing list

List archive

Re: [ocaml-platform] [Coq-Club] Coq opam package


Chronological Thread 
  • From: Gregory Malecha <gmalecha AT eecs.harvard.edu>
  • To: Wojciech Meyer <wojciech.meyer AT gmail.com>
  • Cc: Thomas Refis <thomas.refis AT gmail.com>, Stefan Monnier <monnier AT iro.umontreal.ca>, Coq Club <coq-club AT inria.fr>, platform <platform AT lists.ocaml.org>
  • Subject: Re: [ocaml-platform] [Coq-Club] Coq opam package
  • Date: Wed, 10 Apr 2013 17:55:24 -0400

Unrelated to opam is simply the architectural decision in Coq that vo's have strict dependencies on precise builds of Coq (including the version of OCaml used). I understand that this is possibly eases the implementation of Coq internals, but pulling out the actual code that saves to and reads from a file would benefit anyone who wants to use or distribute Coq libraries.


On Wed, Apr 10, 2013 at 5:17 PM, Wojciech Meyer <wojciech.meyer AT gmail.com> wrote:
Thomas Refis <thomas.refis AT gmail.com> writes:

> Another possibility is to not update a package right away when a knew
> optional dependency is available, but wait for the next "opam
> upgrade". And adding a "--ignore <package>" option to the upgrade
> command would be nice as well.

I agree it would be a useful feature, and might cause errors which we
really try to avoid. As a side note, I had occasions to recompile some
packages when it was *not* really required. Coq compiles quite long, and
I care about compilation time too so reducing that time would be really
good when upgrading dependent packages.

Thanks,
Wojciech



--
gregory malecha
http://www.people.fas.harvard.edu/~gmalecha/



Archive powered by MHonArc 2.6.18.

Top of Page