From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by sympa.inria.fr (Postfix) with ESMTPS id 9886F7EE99 for ; Tue, 10 Dec 2013 02:12:59 +0100 (CET) Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of berenger@riken.jp) identity=pra; client-ip=134.160.33.161; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="berenger@riken.jp"; x-sender="berenger@riken.jp"; x-conformance=sidf_compatible Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of berenger@riken.jp designates 134.160.33.161 as permitted sender) identity=mailfrom; client-ip=134.160.33.161; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="berenger@riken.jp"; x-sender="berenger@riken.jp"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of postmaster@postman.riken.jp designates 134.160.33.161 as permitted sender) identity=helo; client-ip=134.160.33.161; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="berenger@riken.jp"; x-sender="postmaster@postman.riken.jp"; x-conformance=sidf_compatible; x-record-type="v=spf1" X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ArMBAFRqplKGoCGhnGdsb2JhbABZgz+mdZJ0gT0OAQEBAQEICwkJFCiCJQEBBAEyAQU2CgYLCxgJBBIIBwkDAgECATMBERMGAgEBDodeAwkGDbleA4ZxF48XhDMDiUCOVIEwhRWGGIhu X-IPAS-Result: ArMBAFRqplKGoCGhnGdsb2JhbABZgz+mdZJ0gT0OAQEBAQEICwkJFCiCJQEBBAEyAQU2CgYLCxgJBBIIBwkDAgECATMBERMGAgEBDodeAwkGDbleA4ZxF48XhDMDiUCOVIEwhRWGGIhu X-IronPort-AV: E=Sophos;i="4.93,861,1378850400"; d="scan'208";a="40153308" Received: from postman1.riken.jp (HELO postman.riken.jp) ([134.160.33.161]) by mail3-smtp-sop.national.inria.fr with ESMTP; 10 Dec 2013 02:12:57 +0100 Received: from postman.riken.jp (postman1.riken.jp [127.0.0.1]) by postman.riken.jp (Postfix) with SMTP id 553D62588001 for ; Tue, 10 Dec 2013 10:12:54 +0900 (JST) Received: from [172.27.98.103] (rikad98.riken.jp [134.160.214.98]) by postman.riken.jp (Postfix) with ESMTPA id 88EA232A0090 for ; Tue, 10 Dec 2013 10:12:53 +0900 (JST) Message-ID: <52A66A95.2060809@riken.jp> Date: Tue, 10 Dec 2013 10:12:53 +0900 From: Francois Berenger User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 MIME-Version: 1.0 To: caml-list@inria.fr References: <31F4C46854FA4FEAAD2EA09D32A72E23@erratique.ch> <4F5AD22CADED45DBAD26A92D3F2B704D@erratique.ch> <52A61CF6.50609@glondu.net> <52A6268A.2070207@glondu.net> <17DAA674530149C0AEC2F351D95EE185@erratique.ch> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2013.12.10.10615 Subject: Re: [Caml-list] Library installation procedure (for use with OPAM)? On 12/10/2013 06:36 AM, Anthony Tavener wrote: > Thanks for the input, everyone! I see there's not quite one-true-way. > This was part of my confusion when I tried searches and looking at > existing packages. It helps to know that OCamlMakefile or ocamlbuild use > ocamlfind, but hide this detail. From my perspective when this is hidden > it just looks like there are even more packaging mechanisms. > > I can understand Daniel's tact: choose one sensible method. This helps > to force an evolution rather than building up cruft. Certainly making a > META file along with descr/opam/url is somewhat redundant. Isn't it? > > For now though, I'll do my install steps with ocamlfind using a META file. OASIS can automatically generate the META file for you, if I remember well. > It wasn't clear to me that ocamlfind is appropriate for installation, or > even how you would use it. Searching, I mostly get matches for using > ocamlfind to install existing packages, not make something installable. > The "install" subsection of ocamlfind really gives the impression of an > end-user tool, not for a library creator. References are made to the > META file but no description of this file. > > Searching for the META file related to OCaml doesn't fare too well > either. Then I realized "man META" actually gives me exactly what I was > looking for. I didn't expect that, since I'd expect other systems could > have a configuration file called META. > > Anyway, thanks! If there isn't an explanation of packaging libraries > somewhere, maybe I'll make a blog post: "How to share your library". > It's the kind of thing which might seem like nothing once you know it. > > -Tony > > > On Mon, Dec 9, 2013 at 2:04 PM, Daniel Bünzli > > wrote: > > > > Le lundi, 9 décembre 2013 à 21:22, Stéphane Glondu a écrit : > > > Yes, but the existing stuff too. And the packaging work is > (should be) > > mainly adding metadata and integrating with the other packages, > which is > > hardly automatable. What you are talking about is package building, > > which can already be automated with the standard "./configure && > make && > > sudo make install" interface. > > Why not but then provide me *convenient and easily understandable* > tools that allow me to implement this interface in a reliable way. I > don't want to replicate install logic in my twelve and growing > packages, I used to do that but it's too costly in terms of > maintenance. I now found a way of delegating the install logic to a > tool in what I suppose is the main distribution channel for my > packages (and that shouldn't be too hard for other distribution > channels to use), I'm not going back unless something better and as > convenient emerges. > > > > > http://xkcd.com/927/ > > > So what's your proposal then ? > > > > I am not proposing anything new. You are. > > Joke for joke. Besides I'm not proposing anything, I responded to > the original poster's question on how I proceed to install libraries > with OPAM. > > Best, > > Daniel > > > > -- > Caml-list mailing list. Subscription management and archives: > https://sympa.inria.fr/sympa/arc/caml-list > Beginner's list: http://groups.yahoo.com/group/ocaml_beginners > Bug reports: http://caml.inria.fr/bin/caml-bugs > > -- Best regards, Francois Berenger.