Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Experimental fix for mirage/mirage#221 #1673

Merged
merged 2 commits into from Feb 13, 2014

Commits on Feb 12, 2014

  1. Experimental fix for mirage/mirage#221

    This leaves a stray binary after an uninstall, but fixes the
    situation where the `mirage` binary attempts to upgrade itself
    (due to invoking OPAM, which installs some optional dependencies,
    which then proceed to try and recompile mirage).
    
    The only long-term fix is to lift `mirage` into being a host-level
    tool and not tracked by the same tool it uses to install libraries,
    but for the moment renaming the active `mirage` binary to `mirage.old`
    on uninstall should do the trick.
    avsm committed Feb 12, 2014
    Configuration menu
    Copy the full SHA
    800a4ef View commit details
    Browse the repository at this point in the history

Commits on Feb 13, 2014

  1. @samoht points out that a simple rm should be enough here

    The uninstall simply wasn't removing the binary before.
    avsm committed Feb 13, 2014
    Configuration menu
    Copy the full SHA
    3d18111 View commit details
    Browse the repository at this point in the history