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

simon cruanes simon.cruanes.2007 at m4x.org
Wed Apr 10 22:35:00 BST 2013

Could it be possible for some OPAM packages to declare both an
installation, and an update target? For coq, I believe that what takes
time is compiling/type checking the standard library; this doesn't need
to be done again if coq is re-compiled with a GTK interface. If the coq
package provided something to re-compile only coq and not the stdlib,
that would make this less of a problem. But maybe that would complicate
a lot OPAM.



On 10/04/2013 23:17, Wojciech Meyer 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
> _______________________________________________
> Platform mailing list
> Platform at lists.ocaml.org
> http://lists.ocaml.org/listinfo/platform

More information about the Platform mailing list