If the field "build" exists in the .comp file, substitutions are activated. In particular [substitute_string] performs the association of variables (like "%PREFIX%"). However, the state [t] given as argument does not reflect the new version of OCaml, because [install_conf_ocaml] is called after. Here we solve this by initializing the conf-ocaml.config before constructing the compiler.
… are some optimization of usual dependencies, in the sense that for removing, [I_to_recompile] is sometimes returned instead of [I_to_delete]. Then, the full universe can be given to the solver when doing "opam remove". The difficult point is to explicitely and topologically remove packages that are explicitely requested (whether they contain optional packages or not). The current heuristic is to remove the fewer packages.
This resolves partially the issue #69 . In particular, it proposes everytime to remove packages that optionally depend on others (instead of recompiling).
The extlib extensions are unused by anything else in opam (including cudf), so compilation is unaffected
…ins wrong lines taken from the output of "rsync"
…oduced in a22a427 )
… about the initial state.
It contained wrong OCaml version because the state was not updated.
…c links are sometimes encountered in the folding tree
…sitory, we arrive at the same situation as #64 (if moreover the .comp contains "base-..." as packages to install). We propose to desactivate the failure if the option "-no-base-package" has explicitely been set.
… false", we have a confirmation dialog indicating that the OCaml in PATH does not exist or is different than before
…system" is the target
…cept .comp files in repository)
…d treat the result as a warning
… receives an unknown compiler name In particular we split [update] in 2.
…ween the first [update_available_current] and the second
…er directory with no initial .opam/config