This should fix #35
this is better than .../build/_
…n which does not exists
Even if the "universe" given to the solver does not contain packages that are not compatible with the current OCaml version ( changes introduced in 6ff4f04 ), the "request" could still wrongly contain such packages. Then, the solver raises an anormal exception issued from "dose" side. We propose here to filter packages that are available by the current version of OCaml after the computation performed in [load_state]. Futur work : enhance the output of client.ml/list so that it can mark packages that are available with the current OCaml version...
Although no errors have been detected in practice by the author, in theory it should be [t_new] here. Note that "make tests" succeeds before and after.
…lable. For instance, try : opam install $(opam list -short)
…ages" ( for instance, see 640a3ba )
This is helpful when the initial repository is empty (and thus does not contain the description for the base package) as it is the case in the tests.
This was introduced by db7a4b4
…t, so move it away from now on Obvisoulsy, it could be added later on, after the code had been refactored accordingly.
When an url for a dev package is changed, reclone the repository (and recompile all the dependencies)
Now the environment variables can't have more than one ~/.opam/... path
Some errors appear at opam-mk-repo time when [remove] is called after [copy] in ffbb9a7 . Here, we try to perform the call after.
This reverts commit ffbb9a7.