OCAML version 3 (legacy)

[Euan Thoms]

   Thanks for the info, that's interesting. I solved my problem by digging
   up a binary package for OCAML 3.x. But it was not ideal, I think it was
   a 8.3 package when was on a 8.4 system. Also, it was the old pkg
   format, but a pkg2ng brought it into line with pkgng. It's great that
   the new pkgng doesn't block the old packages, and even greater that we
   can pkgng after the initial boot-strapping.
   How would dependency resolution be affected by your suggested method?
   The context of my issue was that I needed a unison built with OCAML
   3.x. I would have thought that the port for unison232 would depend on
   OCAML (as a build dependency) and thet would pull down OCAML 4.x. So
   despite the OPAM provisioning OCAML 3.x, it would require some hacking
   to get it to build unison232.
   In the future, I may provision a FreeBSD 10.x server, and I will not
   find a binary package for OCAML 3.x. Idealy, the OCAML devs should have
   allowed for backwards compatability, like being abl e to create a 3.x
   database. BTW, I don't know anything about OCAML, other than it's
   needed by unison.
   On Tuesday, August 12, 2014 20:53 SGT, Gabor Pali <pgj at FreeBSD.org>
   wrote:


     Hi Euan,
     2014-08-11 17:03 GMT+01:00 Euan Thoms :
     > However, I was suggesting we have a legacy port for OCAML 3.x,
     just
     > like we have for php and other important stuff that newer versions
     > breaks things.
     If you are really in need for the 3.x version of OCaml compiler, you
     may want to try OPAM [1]. That is the ocaml-opam package [2] in the
     FreeBSD repositories.
     Although OPAM is dubbed as a "package manager", it can actually
     manage
     different compiler versions, using its "switch" command [3]. Then
     you
     could install OCaml packages atop that compiler separately, isola
     ted
     from other instances, giving the advantage of working with multiple
     OCaml versions at the same time.
     [1] https://opam.ocaml.org/
     [2] http://www.freshports.org/devel/ocaml-opam
     [3] https://opam.ocaml.org/doc/Advanced_Usage.html