From: Raphael Proust <raphlalou@gmail.com>
To: manu delab <manu.delab@gmail.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] updating opam
Date: Fri, 1 Mar 2013 11:46:41 +0000 [thread overview]
Message-ID: <CAAmHUAnRy4YtuC6fMcJQH7jktc1riNP9wYtR3SdGX033VxSWQA@mail.gmail.com> (raw)
In-Reply-To: <CAAnxNh8fiCyFpBuD5K1cdg00Y1S-U=LWYUif3Z7_roChV5ynDQ@mail.gmail.com>
On Fri, Mar 1, 2013 at 11:41 AM, manu delab <manu.delab@gmail.com> wrote:
> Hello,
>
> Is there a way to update one's version of opam, without having to delete
> .opam folder (and having to recompile again compilers and packages) ?
For all the updates I did, I simply updated the opam program (via
Archlinux's AUR package). The new version of opam just used the old
.opam directory transparently.
Did you try not deleting your .opam?
Does your opam binary live in your .opam? (And if so, you should
consider moving it.)
Did you experience any specific bug when not deleting .opam?
Cheers,
--
______________
Raphaël Proust
prev parent reply other threads:[~2013-03-01 11:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-01 11:41 manu delab
2013-03-01 11:46 ` Raphael Proust [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAAmHUAnRy4YtuC6fMcJQH7jktc1riNP9wYtR3SdGX033VxSWQA@mail.gmail.com \
--to=raphlalou@gmail.com \
--cc=caml-list@inria.fr \
--cc=manu.delab@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).