Skip to Content.
Sympa Menu

coq-club - Re: [Coq-Club] Package managing

coq-club AT inria.fr

Subject: The Coq mailing list

List archive

Re: [Coq-Club] Package managing


Chronological Thread 
  • From: Guillaume Melquiond <guillaume.melquiond AT inria.fr>
  • To: coq-club AT inria.fr
  • Subject: Re: [Coq-Club] Package managing
  • Date: Mon, 14 Oct 2013 14:31:44 +0200

On 12/10/2013 23:59, Thomas Braibant wrote:
the right list of packages. Yet, I really think that we want some
"persistent" coq switches: switching from coq vA to coq vB makes it
possible to install packages for vB, and come back to your coq vA
installation without having to recompile coq vA. (Personally, I used
to think that I would only ever use the latest Coq version, but it
is not the case anymore: sometimes, I use trunk, sometimes I use Coq
patched with mtac, sometimes, I use 8.4pl2 and so on.) So am I right
that we (the coq community) want some persistent switches?

You lost me there. As you said in another part of your email, any sane build system will install vos and plugins to coq-path/user-contrib/contrib-name. So there should not be any need to recompile anything when switching from one version of coq to another, since the compiled files just live in separate directories. In fact, while I use several versions of Coq in my day-to-day work, I never have to recompile anything (until I install a brand new version of Coq or of one of the user contributions, that is).

Best regards,

Guillaume



Archive powered by MHonArc 2.6.18.

Top of Page