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 75CB67EE51 for ; Thu, 30 May 2013 06:52:27 +0200 (CEST) Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of mmatalka@gmail.com) identity=pra; client-ip=209.85.212.171; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="mmatalka@gmail.com"; x-sender="mmatalka@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of mmatalka@gmail.com designates 209.85.212.171 as permitted sender) identity=mailfrom; client-ip=209.85.212.171; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="mmatalka@gmail.com"; x-sender="mmatalka@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-wi0-f171.google.com) identity=helo; client-ip=209.85.212.171; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="mmatalka@gmail.com"; x-sender="postmaster@mail-wi0-f171.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AscCABnaplHRVdSrk2dsb2JhbABZgzmvaIlniDh7CBYOAQEBAQcLCwkUBCSCIwEBBAFAARsSCwEDDAYFBAcNDSEhAQERAQUBChIGEwgKh2gBAwkGDJwHjD+CfYRuChknAwpYiCIBBQyMMIJTBAeDVwOTaoFrgWaBKYp0gz4WKYQ3Og X-IPAS-Result: AscCABnaplHRVdSrk2dsb2JhbABZgzmvaIlniDh7CBYOAQEBAQcLCwkUBCSCIwEBBAFAARsSCwEDDAYFBAcNDSEhAQERAQUBChIGEwgKh2gBAwkGDJwHjD+CfYRuChknAwpYiCIBBQyMMIJTBAeDVwOTaoFrgWaBKYp0gz4WKYQ3Og X-IronPort-AV: E=Sophos;i="4.87,768,1363129200"; d="scan'208";a="16142793" Received: from mail-wi0-f171.google.com ([209.85.212.171]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/RC4-SHA; 30 May 2013 06:52:26 +0200 Received: by mail-wi0-f171.google.com with SMTP id hq7so4143524wib.4 for ; Wed, 29 May 2013 21:52:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=SatK13jBaWbED0mRylKUyPyhxg63KWlGp7DMt8ApxHg=; b=qLynyj1w2tTMc0qzGtQuSTUjs01IyZicW+4LH5Y4KqlA4mZGYOrzjWhGt0rrlGrG37 B2PZ7NK9PfnFH7FdXxzBBYF7wykHathC8ZUytS0bdfnW1nkT4tOVAcPpYATQe9ZCj+vh ood6OoFzVmAYT9k/xE5qySpdBviX6mUElLq4WIx4z2lqMQBJc3tMf87+gByDZmQRJqs7 sXhmDdddzQVQ2EcK6ntFFT52q657Rgck0macTdIiH5fs3aDoo15JgzcDAIGQQP73YxUI e+rGYEtOupH2Wg7t0yFKFoAR0aKjWWU35OXM/+dtAWazWYRqh9eOIXWftl9aNv2YBark 2F+Q== MIME-Version: 1.0 X-Received: by 10.180.19.72 with SMTP id c8mr2817919wie.35.1369889546209; Wed, 29 May 2013 21:52:26 -0700 (PDT) Received: by 10.194.123.231 with HTTP; Wed, 29 May 2013 21:52:25 -0700 (PDT) Received: by 10.194.123.231 with HTTP; Wed, 29 May 2013 21:52:25 -0700 (PDT) In-Reply-To: <1629005.lH05byJ9SH@groupon> References: <20130523235355.GI6510@siouxsie> <87r4gppk3k.fsf@gmail.com> <51A6A13F.901@riken.jp> <1629005.lH05byJ9SH@groupon> Date: Thu, 30 May 2013 06:52:25 +0200 Message-ID: From: Malcolm Matalka To: Chet Murthy Cc: Francois Berenger , caml-list Content-Type: multipart/alternative; boundary=bcaec53d5ae5c88ffe04dde843f7 Subject: Re: Problems to get larger user base ... (Re: [Caml-list] OCaml's variables) --bcaec53d5ae5c88ffe04dde843f7 Content-Type: text/plain; charset=ISO-8859-1 I think out would be wrong for opam to try to solve this problem. There are already many tools available for deploying (Ansible, Puppet, Chef, Fabric, Capistrano). Such a later can be build on top of opam of need be. On May 30, 2013 2:57 AM, "Chet Murthy" wrote: > > On Thursday, May 30, 2013 09:45:51 AM Francois Berenger wrote: > > By the way, is there some plan to support binary packages > > at some point in time with OPAM? > > > > I don't mean OCamlPro distributing them but for an OPAM > > user to be able to create them locally. > > > > That would speedup the process of installing software (given they > > have at least been compiled once). > > This. > > OK. A little more. OPAM is already a tremendous improvement. But to > really make it possible to build -systems- in Ocaml, you have to be > able to distribute collections of programs, config, and libraries, > across multiple (admittedly identical) machines. And distribute > updates to same. OPAM is in some ways like BSD ports -- it works > great for maintaining single machines from source-code. > > But what's needed is a way to maintain -many- machines, and to > distribute updates in a granular manner that be -managed- -- rolled > forward, rolled back, with full knowledge of which versions of which > packages are being installed. And everything with -zero- version > skew. So any nondeterminism happened at buiild-time -- by > deploy-time, all machines are getting identical files with identical > timestamps. > > It's a tall order, b/c OPAM will need to figure out how to capture > enough of the environment (in order to check it on the target machine > where a binary is installed) to verify whether it's safe to install > that binary. But boy would it be nice. > > And as a bonus, we could wrapper opam in the debian apparatus (I > think) and get a really nice way to turn opam packages into debian > packages. > > --chet-- > > > -- > 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 > --bcaec53d5ae5c88ffe04dde843f7 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

I think out would be wrong for opam to try to solve this pro= blem.=A0 There are already many tools available for deploying (Ansible, Pup= pet, Chef, Fabric, Capistrano).=A0 Such a later can be build on top of opam= of need be.

On May 30, 2013 2:57 AM, "Chet Murthy"= <murthy.chet@gmail.com>= wrote:

On Thursday, May 30, 2013 09:45:51 AM Francois Berenger wrote:
> By the way, is there some plan to support binary packages
> at some point in time with OPAM?
>
> I don't mean OCamlPro distributing them but for an OPAM
> user to be able to create them locally.
>
> That would speedup the process of installing software (given they
> have at least been compiled once).

This.

OK. =A0A little more. =A0OPAM is already a tremendous improvement. =A0But t= o
really make it possible to build -systems- in Ocaml, you have to be
able to distribute collections of programs, config, and libraries,
across multiple (admittedly identical) machines. =A0And distribute
updates to same. =A0OPAM is in some ways like BSD ports -- it works
great for maintaining single machines from source-code.

But what's needed is a way to maintain -many- machines, and to
distribute updates in a granular manner that be -managed- -- rolled
forward, rolled back, with full knowledge of which versions of which
packages are being installed. =A0And everything with -zero- version
skew. =A0So any nondeterminism happened at buiild-time -- by
deploy-time, all machines are getting identical files with identical
timestamps.

It's a tall order, b/c OPAM will need to figure out how to capture
enough of the environment (in order to check it on the target machine
where a binary is installed) to verify whether it's safe to install
that binary. =A0But boy would it be nice.

And as a bonus, we could wrapper opam in the debian apparatus (I
think) and get a really nice way to turn opam packages into debian
packages.

--chet--


--
Caml-list mailing list. =A0Subscription management and archives:
ht= tps://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
--bcaec53d5ae5c88ffe04dde843f7--