From owner-freebsd-ports@FreeBSD.ORG  Wed Aug 13 22:27:48 2014
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 5DF1FA8D;
 Wed, 13 Aug 2014 22:27:48 +0000 (UTC)
Received: from comms.potensol.com (comms.potensol.com [203.125.193.120])
 (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits))
 (Client CN "comms.potensol.com", Issuer "comms.potensol.com" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id 16B6E2857;
 Wed, 13 Aug 2014 22:27:47 +0000 (UTC)
Received: from comms.potensol.com (comms.potensol.com [203.125.193.120])
 by comms.potensol.com (Postfix) with ESMTP id BF7DA19DDD;
 Thu, 14 Aug 2014 06:27:45 +0800 (SGT)
Received: from comms.potensol.com (comms.potensol.com [203.125.193.120])
 by comms.potensol.com (Postfix) with ESMTP id 58E3019DDC;
 Thu, 14 Aug 2014 06:27:45 +0800 (SGT)
User-Agent: SOGoMail 2.0.4b
X-Forward: 203.125.193.120
from: "Euan Thoms" <euan@potensol.com>
subject: Re: OCAML version 3 (legacy)
message-id: <f33c-53ebe680-5-6b8b4580@234960846>
to: "Gabor Pali" <pgj@FreeBSD.org>
date: Wed, 13 Aug 2014 22:27:44 +0000
in-reply-to: <CAHnG2CxMaCBJyYbUD65EMFLvB2u0CJZpTC6QW9LJP6=MYTQtzg@mail.gmail.com>
X-Virus-Scanned: ClamAV using ClamSMTP
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1
Cc: =?utf-8?q?Michael_Gr=C3=BCnewald?= <michipili@gmail.com>,
 FreeBSD Ports <ports@freebsd.org>
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Aug 2014 22:27:48 -0000

   > 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.