Date: Wed, 13 Aug 2014 23:10:37 +0100 From: Gabor Pali <pgj@FreeBSD.org> To: Euan Thoms <euan@potensol.com> Cc: =?UTF-8?Q?Michael_Gr=C3=BCnewald?= <michipili@gmail.com>, FreeBSD Ports <ports@freebsd.org> Subject: Re: OCAML version 3 (legacy) Message-ID: <CAHnG2CxMaCBJyYbUD65EMFLvB2u0CJZpTC6QW9LJP6=MYTQtzg@mail.gmail.com> In-Reply-To: <f33c-53ebd880-3-6b8b4580@234960845> References: <CAHnG2Czv3LhNamS7o3B7_7kqvipRra17L8%2BqtgOLxRMOVzTORA@mail.gmail.com> <f33c-53ebd880-3-6b8b4580@234960845>
next in thread | previous in thread | raw e-mail | index | archive | help
2014-08-13 22:29 GMT+01:00 Euan Thoms <euan@potensol.com>: > How would dependency 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?CAHnG2CxMaCBJyYbUD65EMFLvB2u0CJZpTC6QW9LJP6=MYTQtzg>