Re: Conflicting installation advice - not really, your choice
| Newsgroups | gmane.comp.lang.ocaml.beginners |
|---|---|
| Message-ID | <[email protected]> |
On 16.08.2015 14:09, 'Mr. Herr' [email protected] [ocaml_beginners] wrote: > I like the self contained opam+ocaml install too, because I also noticed unwanted > interference between packages > installed using the OS package manager, and ocaml/opam packages. > > Not even the "ocamlrun" runtime for bytecode compiled files is helpful (thinking "hey > I only need ocamlrun on my machines"), > because the binary and also the compiled bytecode are both versioned and must match. > > So now for the self contained opam+ocaml install - this works fine for me, just did > it again in a VM: > > Get the opam binary: see http://opam.ocaml.org/doc/Install.html "Binary installer". I > usually copy the link > and download the file with wget. > > You'd better do chmod +x on the file, then run it as root: ./opam_installer.sh > /usr/local/bin > > Now look at /usr/local/bin, the newest binary from github should be there, compiled > to native code, portable. Just rethinking this part: why should we install the opam binary on a server public path, and all the opam packages in your own $HOME? This only makes sense on a machine with several programmers *each having his own ~/.opam directory* ! So without a shared opam/ directory it makes more sense putting the opam binary into ~/bin /Str.