Date: Wed, 13 Aug 2014 22:27:44 +0000 From: "Euan Thoms" <euan@potensol.com> To: "Gabor Pali" <pgj@FreeBSD.org> Cc: =?utf-8?q?Michael_Gr=C3=BCnewald?= <michipili@gmail.com>, FreeBSD Ports <ports@freebsd.org> Subject: Re: OCAML version 3 (legacy) Message-ID: <f33c-53ebe680-5-6b8b4580@234960846> In-Reply-To: <CAHnG2CxMaCBJyYbUD65EMFLvB2u0CJZpTC6QW9LJP6=MYTQtzg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Why? Will not the net/unison232 or the net/unison port simply work?
> They should be using the latest version of lang/ocaml already.
Yes, the unison232 will built and work with the OCAML in the tree.
However with unison, it's critical that the client and server version
matches. that's why I'm still on 2.32.52, because i have a couple
hundred deployed clients potentially using unison. It seems that not
only must the unison version match exactly, but the OCAML database it
uses must also match. Or at least it must be compatable. OCAML 4.x
databases are not compatable with 3.x. Hence the problem. Perhaps there
are other ports out there that OCAML 4.x causes breakage.
On Thursday, August 14, 2014 06:10 SGT, Gabor Pali <pgj@FreeBSD.org>
wrote:
2014-08-13 22:29 GMT+01:00 Euan Thoms :
> How would dep endency resolution be affected by your suggested
method?
OPAM manages the dependencies itself, without involving pkg(8). For
what it is worth, you should be able to install unison via OPAM
easily. Though, it will not put the unison binary to under
/usr/local/bin but somewhere around ~/.opam/bin instead.
> The context of my issue was that I needed a unison built with
OCAML 3.x.
Why? Will not the net/unison232 or the net/unison port simply work?
They should be using the latest version of lang/ocaml already.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f33c-53ebe680-5-6b8b4580>