From: Anil Madhavapeddy <anil@recoil.org>
To: "Sébastien Hinderer" <Sebastien.Hinderer@inria.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Opam: using both 1.2 and 2.0
Date: Mon, 21 Jan 2019 16:08:58 +0000 [thread overview]
Message-ID: <44380FFC-CFBB-4489-9055-354DB367A43C@recoil.org> (raw)
In-Reply-To: <20190121145421.GA6390@prajna.paris.inria.fr>
On 21 Jan 2019, at 14:54, Sébastien Hinderer <Sebastien.Hinderer@inria.fr> wrote:
>
> Hi,
>
> Daniel Bünzli (2019/01/07 10:52 +0100):
>> On 7 January 2019 at 10:25:10, Sébastien Hinderer (sebastien.hinderer@inria.fr) wrote:
>>
>>> Will try that! Thanks! But still have to figure out how to install opam
>>> 1 I guess, because it will probably not be possible to install it
>>> through the distribution's package manager.
>>
>> opam dev's are kind enough to provide you with a selection of binaries here:
>>
>> https://github.com/ocaml/opam/releases/tag/1.2.2
>>
>> I never tried them though. Otherwise given an OCaml install, compiling
>> from the tarball should be easy has never been a problem since it's
>> self-contained.
>
> I just wanted to thank you for the suggestion and confirm that it worked
> quite well. I downloaded the binary for my platform and installed it in my
> private bin directory as 'opam1'. When I want to use it, rather than the
> system-provided opam (version 2), I create a symlink in my bin
> directory.
>
> Then I just had to do:
>
> opam init --root=~/.opam1
>
> and everything wored fine.
>
Excellent, glad to hear that’s working for you now!
In the medium-term, please do let us opam developers know if there is
some fundamental reason why you cannot migrate your projects from
opam 1 to 2. We will do our best to unblock it in opam 2, since we
can’t fully leave opam 1 behind until the last user has closed the door
behind them :-)
regards,
Anil
next prev parent reply other threads:[~2019-01-21 16:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-07 8:12 Sébastien Hinderer
2019-01-07 9:22 ` Daniel Bünzli
2019-01-07 9:25 ` Sébastien Hinderer
2019-01-07 9:52 ` Daniel Bünzli
2019-01-07 23:24 ` Jacques Garrigue
2019-01-21 14:54 ` Sébastien Hinderer
2019-01-21 16:08 ` Anil Madhavapeddy [this message]
2019-01-07 15:50 ` Hendrik Boom
2019-01-07 21:11 ` Sébastien Hinderer
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=44380FFC-CFBB-4489-9055-354DB367A43C@recoil.org \
--to=anil@recoil.org \
--cc=Sebastien.Hinderer@inria.fr \
--cc=caml-list@inria.fr \
/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