From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31089 invoked by alias); 11 Jun 2013 15:37:35 -0000 Mailing-List: contact cygwin-apps-help@cygwin.com; run by ezmlm Precedence: bulk Sender: cygwin-apps-owner@cygwin.com List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps@cygwin.com Received: (qmail 31076 invoked by uid 89); 11 Jun 2013 15:37:35 -0000 X-Spam-SWARE-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RP_MATCHES_RCVD autolearn=ham version=3.3.1 Received: from mail2-relais-roc.national.inria.fr (HELO mail2-relais-roc.national.inria.fr) (192.134.164.83) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Tue, 11 Jun 2013 15:37:34 +0000 Received: from wifi-eduroam-160217.inria.fr ([128.93.160.217]) by mail2-relais-roc.national.inria.fr with ESMTP/TLS/AES128-SHA; 11 Jun 2013 17:37:32 +0200 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1283) Subject: Re: [RFU] ocaml-4.00.1-1 From: Damien Doligez In-Reply-To: <20130610082700.GA28431@calimero.vinschen.de> Date: Tue, 11 Jun 2013 15:37:00 -0000 Content-Transfer-Encoding: 7bit Message-Id: <45D0C28C-DE97-4128-B54F-9D632D4B13A7@inria.fr> References: <03567512-0765-4AA9-9316-92AA3D5D71EE@inria.fr> <8DC287A3-12E5-4AF7-AFFB-647396555DB0@inria.fr> <20130607141924.GC22187@calimero.vinschen.de> <20130610082700.GA28431@calimero.vinschen.de> To: cygwin-apps@cygwin.com X-SW-Source: 2013-06/txt/msg00119.txt.bz2 Hi Corinna, > Given what Yaakov said, wouldn't it make sense to provide the former > ocaml libs and start using a versioned runtime lib approach? I'm not sure I understand exactly what you mean, but providing several versions of the libraries is not going to work because they are strongly tied to the compiler version. If we want different versions of the libraries to coexist, I think the only simple solution is to use a new package name for each release of OCaml. That would probably force every library to follow the same pattern, leading to a confusing proliferation of packages. The strong typing of OCaml gives strong guarantees to the users and imposes strong constraints on linking. Stronger than can be handled by "normal" package managers. This problem has been studied and solved for the Debian package manager [1] but the solution is heavy-weight. Nowadays, the preferred solution among OCaml developers is to use OPAM, a dedicated package manager for OCaml programs and libraries. -- Damien [1] http://jfla.inria.fr/2010/actes/PDF/dogguy.pdf