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: Thomas Gazagnaire <thomas AT ocamlpro.com>
  • To: François Bobot <francois.bobot AT cea.fr>
  • 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: Thu, 11 Apr 2013 15:29:37 +0200

>>> The fact that you don't have a choice when installing a package to
>>> update all the package that may use it or not, is imho really
>>> frustrating. I have indeed had to recompile coq a few times as well,
>>> and the experience gets more annoying every time.
>>
>> The solution for coq is to declare `labgtk` as an optional build-time
>> dependency (eg. simply remove it from the list of optional link-time
>> dependency, but let the right option in the configure invocation).
>>
>
> Interesting, it is quite simple.
>
> But is it right that if you do that, when there is an important fix of
> lablgtk you will have to explicitly run "opam reinstall coq" and all the
> coq stdlib will be recompiled?
>
> If it's true it is a nice and simple halfway solution.

If lablgtk does not appear in the list of dependencies (and optional
dependencies), coq will never be recompiled automatically when you upgrade
lablgtk. And if you do "opam reinstall coq" OPAM will indeed recompile the
whole package.

Tracking dependencies at a finer grain that the package level requires build
system hooks that OPAM doesn't have (yet?).

Best,
Thomas




Archive powered by MHonArc 2.6.18.

Top of Page