Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Commits on Jan 15, 2013
  1. Bump version number

  2. Update CHANGES

  3. Merge pull request #387 from mehdid/master

    Pcre was renamed into Re_pcre
  4. Update to ocaml-re 1.2.0

    This is related to #387
Commits on Jan 14, 2013
  1. Fix initialization.

    Check the consistency of base-package only when we switch.
    This should fix #390
  2. Merge pull request #389 from chambart/master

    Format the install request build in opamClient so that an external cudf solver can solve it correctly
  3. @chambart
  4. More stats

Commits on Jan 13, 2013
  1. Merge pull request #388 from tuong/master

    we continue 995cea3
  2. @tuong

    we continue 995cea3

    tuong authored
    The fix-point is really really 1 step now.
  3. Add a patch to make dose use the new re.pcre API instead of pcre-ocaml.

    This is not activated yet as need to wait for upstream changes and #387.
  4. @mehdid

    Pcre was renamed into Re_pcre

    mehdid authored
Commits on Jan 12, 2013
Commits on Jan 11, 2013
  1. Fix 'opam pin --force'

  2. Better message when the version of OPAM is not up-to-date.

    It's maybe a bit harsh to beg the user to upgrade on every opam invocation, but I guess we could improve that with 1.0.0.
    This should fix #382
  3. Improve the pin consistency checks, and consider that the pinned pack…

    …age is the one with max-version. I guess it would be better to give the option to the user to choose which is the corresponding version but no hurry.
  4. On startup check that repository state are consistent and try to fix …

    …eventual issues.
    This could be extended later by adding more consistency checks.
  5. Add consistency checks when using 'opam pin'.

    This will make the semantics easier to understand (but one could still use --force to bypass the checks).
    This should fix #384
  6. Always create a new archive from 'git -tar' when using dev packages, …

    …this is much more robust (and it not much slower anyway).
  7. On upgrade, if we recompile packages because of upstream changes (whi…

    …ch is typically the case when we use dev packages), remember which packages successfuly build and install to not have to handle them again on the next upgdrade.
    This was working well when we were upgrading because of new packages, so now the behavior is much more consistent.
  8. Clean up log files when the command is a success, and do not polute t…

    …he root of OPAM (ie. everything goes into ~/.opam/log or ~/.opam/<switch>/build/<package>/)
Something went wrong with that request. Please try again.