opam
Here are 54 public repositories matching this topic...
-
Updated
Oct 27, 2020 - OCaml
-
Updated
Oct 10, 2020 - OCaml
-
Updated
Sep 24, 2020 - OCaml
-
Updated
Nov 15, 2018 - Shell
-
Updated
Sep 10, 2020 - Shell
-
Updated
Oct 27, 2020 - JavaScript
-
Updated
Nov 26, 2017 - Shell
-
Updated
Mar 15, 2020 - OCaml
As OPAM 2.1 automatically removes installed files, opam install subcommand is meaningless.
As of 2.0, opam tracks the files added to the prefix during package installation, and automatically removes them on package removal, so this should not be needed anymore in most cases (and may even be harmful if files from different packages overlap, which remove scripts generally don't handle). Use i
-
Updated
Oct 12, 2020 - Dockerfile
-
Updated
Dec 18, 2019 - Dockerfile
-
Updated
Aug 15, 2017 - Shell
idea: add a boolean option that would trigger extra commands such as those of this Travis CI template
see coq-community/templates#28 (comment) for more context
-
Updated
Aug 28, 2020 - Dockerfile
Improve this page
Add a description, image, and links to the opam topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the opam topic, visit your repo's landing page and select "manage topics."
Dune systematically buffers the output of commands so that their output is not mixed up during parallel builds. However, this is not ideal for interactive commands that require direct access to the terminal.
Currently, the only workaround is to run dune with
-j 1 --no-bufferwhich is not ideal since it completely disables parallelism and also require a specific dune invocation.Another ide