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 mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id 8C8E37EE63 for ; Thu, 30 May 2013 09:51:28 +0200 (CEST) Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of thomas.gazagnaire@gmail.com) identity=pra; client-ip=209.85.212.176; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="thomas.gazagnaire@gmail.com"; x-sender="thomas.gazagnaire@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of thomas.gazagnaire@gmail.com designates 209.85.212.176 as permitted sender) identity=mailfrom; client-ip=209.85.212.176; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="thomas.gazagnaire@gmail.com"; x-sender="thomas.gazagnaire@gmail.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@mail-wi0-f176.google.com) identity=helo; client-ip=209.85.212.176; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="thomas.gazagnaire@gmail.com"; x-sender="postmaster@mail-wi0-f176.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Au4BACYEp1HRVdSwjWdsb2JhbABZgzkBwwMWDgEBAQEHCwsJEgYkgiMBAQQBOgYBOAEDDAEFQAs0AQUBHAaIDgMJBgQIm2uPPIUTJw2IegEBBAySBGEDk2qJb4k9P4FdgSGBOQ X-IPAS-Result: Au4BACYEp1HRVdSwjWdsb2JhbABZgzkBwwMWDgEBAQEHCwsJEgYkgiMBAQQBOgYBOAEDDAEFQAs0AQUBHAaIDgMJBgQIm2uPPIUTJw2IegEBBAySBGEDk2qJb4k9P4FdgSGBOQ X-IronPort-AV: E=Sophos;i="4.87,769,1363129200"; d="scan'208";a="19572986" Received: from mail-wi0-f176.google.com ([209.85.212.176]) by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/RC4-SHA; 30 May 2013 09:51:28 +0200 Received: by mail-wi0-f176.google.com with SMTP id hr14so4256263wib.15 for ; Thu, 30 May 2013 00:51:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=Jfcybu1+XYF8n0Hw7FMNhnR5f/yG/Og5GzxULE7JyBc=; b=B8O2Te4qhmerX0uILfzybnzuu9Nf5UMdTuTURs0x+PIxfr9oFs0Qu5T+vtdBKtdkD7 LFaW0XW07GTdOo8I9SVi+hrrPlIV8yG3GHfCWG0RkURmYEx6Y0YNnrwGfi7GrBXHqL50 NA6+rNuDLbozr+7h8ZUcxJaiC7lStL8ewYORsIJsWg7FX4k503Q582gMvBE0yuv+ARDy Fnui1mC5LEGMFk/6xuqo4ji+U5hJWIWv7HdBJu4xA4j9MSPOP3eWHA71WrzA7D/Sqbdc fAeEYWPiDR4/Phy9PRTNMD/bwMwyjZp/75pdfbz0uB1mikyP8U6PjSxGnj7mwa1h8mK5 dB3Q== X-Received: by 10.180.211.49 with SMTP id mz17mr16944016wic.43.1369900287795; Thu, 30 May 2013 00:51:27 -0700 (PDT) Received: from [10.35.195.146] ([213.30.181.210]) by mx.google.com with ESMTPSA id k10sm36124255wia.4.2013.05.30.00.51.26 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 30 May 2013 00:51:27 -0700 (PDT) Sender: Thomas Gazagnaire Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Thomas Gazagnaire In-Reply-To: <1629005.lH05byJ9SH@groupon> Date: Thu, 30 May 2013 09:51:25 +0200 Cc: caml-list@inria.fr, Francois Berenger Content-Transfer-Encoding: quoted-printable Message-Id: <86D3B9E0-5882-48FB-8701-1AAE86902BBC@ocamlpro.com> References: <20130523235355.GI6510@siouxsie> <87r4gppk3k.fsf@gmail.com> <51A6A13F.901@riken.jp> <1629005.lH05byJ9SH@groupon> To: Chet Murthy X-Mailer: Apple Mail (2.1085) Subject: OPAM binary packages (was Re: Problems to get larger user base ... (Re: [Caml-list] OCaml's variables)) This thread is diverging quite a lot :-) >> By the way, is there some plan to support binary packages >> at some point in time with OPAM? >>=20 >> I don't mean OCamlPro distributing them but for an OPAM >> user to be able to create them locally. >>=20 >> That would speedup the process of installing software (given they >> have at least been compiled once). >=20 > This. >=20 > [..] >=20 > 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. We are indeed in the process of experimenting with that idea (see [1]). Not= hing is ready yet, but that's definitely something we are interested in. The hard part is (as always) to keep track of the correct external dependen= cies (such as the available shared C libraries available at the time of bui= ld). A good first approximation is to say that the external dependencies ne= ver change, but that's obviously not very safe to rely on that assumption t= oo much, so we are thinking of keeping track of the result given by ldd as = well. Best, Thomas [1] https://github.com/venator/opam/blob/binary/src/core/opamBinary.ml