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: Wojciech Meyer <wojciech.meyer AT gmail.com>
  • To: Anil Madhavapeddy <anil AT recoil.org>
  • Cc: Thomas Refis <thomas.refis AT gmail.com>, coq-club AT inria.fr, platform <platform AT lists.ocaml.org>, Stefan Monnier <monnier AT iro.umontreal.ca>
  • Subject: Re: [ocaml-platform] [Coq-Club] Coq opam package
  • Date: Wed, 10 Apr 2013 23:12:46 +0100

Anil Madhavapeddy
<anil AT recoil.org>
writes:

> The issue with not recompiling dependent packages immediately is
> that you leave your build environment with inconsistent packages
> (since the library CRCs may no longer match). OPAM is conservative
> about not breaking ABI invariants by default, which seems wiser than
> a few unnecessary recompilations at this stage.
>
> I'd be inclined to figure out a mechanism to decouple Coq IDE from
> Coq in the packaging a little more, rather than complicate the
> optional dependency constraint analysis even more.

I think the biggest chalenge here would be to make people to use this
techniques (splitting bigger packages) when it's not always clear how it
should be done. I already started to think that Coq IDE deserves a
separate OPAM package, and my worry is that it's bit unclear how to do
this. So maybe theorems, could be also decoupled and put under different
name. Otherwise I agree, it would better.

-Wojciech



Archive powered by MHonArc 2.6.18.

Top of Page