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 40C927EE99 for ; Mon, 9 Dec 2013 17:40:20 +0100 (CET) Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of sebastien.mondet@gmail.com) identity=pra; client-ip=74.125.82.46; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="sebastien.mondet@gmail.com"; x-sender="sebastien.mondet@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of sebastien.mondet@gmail.com designates 74.125.82.46 as permitted sender) identity=mailfrom; client-ip=74.125.82.46; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="sebastien.mondet@gmail.com"; x-sender="sebastien.mondet@gmail.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of postmaster@mail-wg0-f46.google.com) identity=helo; client-ip=74.125.82.46; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="sebastien.mondet@gmail.com"; x-sender="postmaster@mail-wg0-f46.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvcCABbypVJKfVIulWdsb2JhbABZgz9Tgn+2FoEnCBYOAQEBAQcNCQkSKoIlAQEEASMdARsdAQMBCwYFCzcCAiIBEQEFARwGEwiHZwEDCQamDYwGU4MJhB0KGScNZIYDEQEFDI8EB4JrgUgDiUKOUoEwjnYYKYRzHg X-IPAS-Result: AvcCABbypVJKfVIulWdsb2JhbABZgz9Tgn+2FoEnCBYOAQEBAQcNCQkSKoIlAQEEASMdARsdAQMBCwYFCzcCAiIBEQEFARwGEwiHZwEDCQamDYwGU4MJhB0KGScNZIYDEQEFDI8EB4JrgUgDiUKOUoEwjnYYKYRzHg X-IronPort-AV: E=Sophos;i="4.93,859,1378850400"; d="scan'208";a="40097186" Received: from mail-wg0-f46.google.com ([74.125.82.46]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/RC4-SHA; 09 Dec 2013 17:40:11 +0100 Received: by mail-wg0-f46.google.com with SMTP id m15so3651151wgh.25 for ; Mon, 09 Dec 2013 08:40:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=HMnu0LMR5/3eM0ng2eELg1z7VnVhJj8fYhUCuvxED2o=; b=XpZfTev2ssyer7JkXE6pdr+6fH5Oc2+SJMjrLOHtWq9eGXVlTdglL60n3xzDMR+cld OYU1IfHVW5oC00jCDj1P0Kxl7+Abax3VU7cz82Nyu/duX1e8v6qfKhYysm+50XfEiSmC 2w12c6xHz3tAPTTTUwRgwAQSepXpTem6LfGON56Gfb9HVZQmc06V8Fw11HbnNkdAgnFZ hil+s1cvllgALZiswxHS4aiPscakosqec5gWDpVT7Nfu5AMeEn0I8f07dh6bdShnIWEw ahE/FJ+JA+n/kcoCmWyX5fg2ahJChgxMTlsVpOdYaCfUfBOvDTLIxZL0SB++L87yGzPc iDLA== X-Received: by 10.194.119.132 with SMTP id ku4mr35524450wjb.51.1386607209614; Mon, 09 Dec 2013 08:40:09 -0800 (PST) MIME-Version: 1.0 Received: by 10.216.70.202 with HTTP; Mon, 9 Dec 2013 08:39:49 -0800 (PST) In-Reply-To: <31F4C46854FA4FEAAD2EA09D32A72E23@erratique.ch> References: <31F4C46854FA4FEAAD2EA09D32A72E23@erratique.ch> From: Sebastien Mondet Date: Mon, 9 Dec 2013 11:39:49 -0500 Message-ID: To: =?UTF-8?Q?Daniel_B=C3=BCnzli?= Cc: Anthony Tavener , "caml-list@inria.fr" Content-Type: multipart/alternative; boundary=089e01228d722c148904ed1ca641 Subject: Re: [Caml-list] Library installation procedure (for use with OPAM)? --089e01228d722c148904ed1ca641 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Mon, Dec 9, 2013 at 10:57 AM, Daniel B=C3=BCnzli wrote: > > > Le lundi, 9 d=C3=A9cembre 2013 =C3=A0 16:23, Sebastien Mondet a =C3=A9cri= t : > > > Opam's .install files should be used only to fix packages whose > installation is already broken or unsufficient, shouldn't it? > > Where did you get that from ? > > A .install file is a good way of specifying what you want to install > without having to replicate any installation logic in your package which = is > good when you develop and distribute many packages and need to scale. > > > If you rely *only* on the .install, your package can be installed only > with opam, it will break for other users (GODI, WODI, Manual Package > Management=E2=84=A2, etc.). > > It can be installed by anything that understands what a .install file is, > there's nothing specific to opam here. Godi is shutting down, Wodi could = be > make to understand .install file. Manual Package Management=E2=84=A2, the= file > format of .install is very simple you could perfectly develop have a > command line tool that reads it and issues the appropriate cp commands, I= 'm > personally no longer interested in that form of package management and > don't have the time to support it. > > So, if everybody else have to implement them, opam's install files become a new standard for the OCaml cummunity? Do most of us agree? (I'm not against it, I just don't want to rely on 50 different standards). (BTW, since you generate those .install files you could have generated install.sh files doing the 'cp's as easily ;) ) > I think it's good hygiene to at least provide an ocamlfind-based > installation of the libraries. > > As I said `ocamlfind install` doesn't allow you to install binaries, man > pages, configuration files, documentation etc. With a .install file you c= an > specify what you want to be installed to the classic unix paths (bin, etc, > man, share, etc.). > > yes but in practice `ocamlfind install` is enough to make most dependencies of a given package work (a few times a `cp exec $BIN` is also needed indeed). (A while ago, before opam, a new version of GODI broke on our main platform because of some ocamlnet configuration bug, but I was able to reinstall ocaml and about 25 third-party libraries and syntax extensions from scratch without too much pain =E2=86=92 we see great value in that package-manageme= nt independence) > Best, > > Daniel > > > --089e01228d722c148904ed1ca641 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable



On Mon, Dec 9, 2013 at 10:57 AM, Daniel B=C3=BCnzli <dan= iel.buenzli@erratique.ch> wrote:


Le lundi, 9 d=C3=A9cembre 2013 =C3=A0 16:23, Sebastien Mondet a =C3=A9crit = :

> Opam's .install files should be used only to fix packages whose in= stallation is already broken or unsufficient, shouldn't it?

Where did you get that from ?

A .install file is a good way of specifying what you want to install withou= t having to replicate any installation logic in your package which is good = when you develop and distribute many packages and need to scale.

> If you rely *only* on the .install, your package can be installed only= with opam, it will break for other users (GODI, WODI, Manual Package Manag= ement=E2=84=A2, etc.).

It can be installed by anything that understands what a .install file= is, there's nothing specific to opam here. Godi is shutting down, Wodi= could be make to understand .install file. Manual Package Management=E2=84= =A2, the file format of .install is very simple you could perfectly develop= have a command line tool that reads it and issues the appropriate cp comma= nds, I'm personally no longer interested in that form of package manage= ment and don't have the time to support it.



So, if everybody else h= ave to implement them, opam's install files become a new standard for t= he OCaml cummunity? Do most of us agree? (I'm not against it, I just do= n't want to rely on 50 different standards).

(BTW, since you generate those .install files you= could have generated install.sh files doing the 'cp's as easily ;)= )


> I think it's good hygiene to at least provide an ocamlfind-based i= nstallation of the libraries.

As I said `ocamlfind install` doesn't allow you to install binari= es, man pages, configuration files, documentation etc. With a .install file= you can specify what you want to be installed to the classic unix paths (b= in, etc, man, share, etc.).


yes but in practice `ocamlfind install= ` is enough to make most dependencies of a given package work (a few times = a `cp exec $BIN` is also needed indeed).

(A while ago, be= fore opam, a new version of GODI broke on our main platform because of some= ocamlnet configuration bug, but I was able to reinstall ocaml and about 25= third-party libraries and syntax extensions from scratch without too much = pain =E2=86=92 we see great value in that package-management independence)<= br>



=C2=A0
Best,

Daniel



--089e01228d722c148904ed1ca641--