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 mail1-relais-roc.national.inria.fr (mail1-relais-roc.national.inria.fr [192.134.164.82]) by sympa.inria.fr (Postfix) with ESMTPS id DC4527EEAF for ; Tue, 22 Jan 2013 16:57:58 +0100 (CET) Received-SPF: None (mail1-smtp-roc.national.inria.fr: no sender authenticity information available from domain of thomas.gazagnaire@gmail.com) identity=pra; client-ip=209.85.212.177; receiver=mail1-smtp-roc.national.inria.fr; envelope-from="thomas.gazagnaire@gmail.com"; x-sender="thomas.gazagnaire@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail1-smtp-roc.national.inria.fr: domain of thomas.gazagnaire@gmail.com designates 209.85.212.177 as permitted sender) identity=mailfrom; client-ip=209.85.212.177; receiver=mail1-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 (mail1-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@mail-wi0-f177.google.com) identity=helo; client-ip=209.85.212.177; receiver=mail1-smtp-roc.national.inria.fr; envelope-from="thomas.gazagnaire@gmail.com"; x-sender="postmaster@mail-wi0-f177.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApUBAO+1/lDRVdSxjWdsb2JhbABEgzioGZJhFg4BAQEBCQkLCRIGI4IeAQEEAToGAS0LAQMBCwEFBRgNITQBBQEKEgYTEod1AwkGDJ5KjiWBCoUcJwMKiFwBBQyQSWEDlyiET4h9P4FYgj8 X-IronPort-AV: E=Sophos;i="4.84,515,1355094000"; d="scan'208";a="191129197" Received: from mail-wi0-f177.google.com ([209.85.212.177]) by mail1-smtp-roc.national.inria.fr with ESMTP/TLS/RC4-SHA; 22 Jan 2013 16:57:58 +0100 Received: by mail-wi0-f177.google.com with SMTP id hm2so6051129wib.4 for ; Tue, 22 Jan 2013 07:57:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=e10a92ZKp6IdtjWGPoGqTLhnSNPZZ12J29Nn2GOS0MI=; b=XD93Lz9AV2YIA9vVieWVMkj84a3atWn/tPskxoFPVgqk/fYJv0x5lk5bel8YOQWvIm nK89yM40VWWAK3bAuyERYEE8x+qQJ3JWPIkC4KtWQI2s7BRJY1MbZnFTJ4Cq32Px06sD pEGi6inHPKL3soRh52knwAwbSzvPiWShbCx3XHXsegij+ZLKwi5FWs4cSBn9SgONmNu/ GPOy6P6BzuY4IFmJlsbL2hwnt6cElQLI0FHMeGkA6EP0mBbo+IPpULdNCDV+26n4Xz++ w4POaSaB5/fLeVAikACyInbZ6xJRtOmHPXGFw5ZwKullsGFuIIsAePfpOtth3zdAevOA zrXg== X-Received: by 10.180.106.34 with SMTP id gr2mr22156777wib.18.1358870276768; Tue, 22 Jan 2013 07:57:56 -0800 (PST) Received: from [10.0.0.84] (volstagg-0.srg.cl.cam.ac.uk. [128.232.32.232]) by mx.google.com with ESMTPS id p2sm24472628wic.7.2013.01.22.07.57.55 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 22 Jan 2013 07:57:55 -0800 (PST) Sender: Thomas Gazagnaire Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Thomas Gazagnaire In-Reply-To: <50F9280F.8070707@gmail.com> Date: Tue, 22 Jan 2013 15:57:54 +0000 Cc: caml-list@inria.fr Content-Transfer-Encoding: quoted-printable Message-Id: <3FBBEB72-F1E2-42C8-AF39-CCA8DCA8628A@ocamlpro.com> References: <6833F17C-B642-4ED9-8C8F-2665A9742845@ocamlpro.com> <50F831B6.6020404@frisch.fr> <224865B3-055C-4E03-AA42-9F962AD516D7@recoil.org> <50F92486.2020704@frisch.fr> <50F9280F.8070707@gmail.com> To: Fabrice Le Fessant X-Mailer: Apple Mail (2.1085) Subject: Re: [Caml-list] [ANN] beta-release of OPAM > Have we started an FAQ for OPAM ? I've created a FAQ with these two questions on OPAM wiki: https://github.co= m/OCamlPro/opam/wiki/FAQ Feel free to edit and contribute! (once we get sufficiently nice contents, this can automatically go somewher= e on opam.ocamlpro.com as the other wiki pages). -- Thomas >=20 > Sounds like the two questions and answers would deserve to be included in= such an FAQ (with a copy on StackOverflow). >=20 > --Fabrice >=20 >=20 > On 01/18/2013 11:42 AM, Anil Madhavapeddy wrote: >> On 18 Jan 2013, at 10:31, Alain Frisch wrote: >>=20 >>> On 01/17/2013 06:22 PM, Anil Madhavapeddy wrote: >>>> I added `opam switch 4.01.0dev+trunk` recently, which will grab the la= test trunk snapshot. >>>> To reinstall it and refresh to a newer snapshot, just do `opam switch = reinstall 4.01.0dev+trunk`, which will also attempt to recompile any packag= es you had in there before. >>>=20 >>> Thanks, this is exactly what I wanted! >>>=20 >>> Shouldn't the package be called simply "trunk", without a reference to = a version number? >>=20 >> Yeah, but OPAM also has compiler version constraints, so that you can ma= rk a package as requiring {>=3D4.00} for example. If the package is just m= arked trunk, then we need to manually record the version number somewhere. >>=20 >> One option is to have a very high version, so that any packages with a l= ower bound will continue to work. The other option (which I chose) is to p= ick the current working version, since compiler releases only happen a coup= le of times a year. We can improve on this... >>=20 >>> I've started to play with opam a little bit, and it's a surprisingly pl= easant experience. Thanks to everyone who contributed to this project! >>>=20 >>> Now I want to create my first package. I've followed the instructions = from http://opam.ocamlpro.com/doc/Packaging.html but I don't know where to = find opam-mk-repo (I've installed opam from the amd64 linux binary). >>=20 >> (that binary is hopefully just a stopgap until the OPAM binary packages = become more widely available) >>=20 >> opam-mk-repo is installed as part of OPAM, so you'll need to install fro= m source. However, you don't actually need to create a repository unless y= ou want to host a mirror of the tarballs. Simply try this: >>=20 >> $ mkdir -p my-repo/packages >> $ opam remote add localdev my-repo >> >> $ opam update >> >> $ opam install >>=20 >> The same applies for compilers. >>=20 >> If you specify a git:// or darcs:// URL in the package `url` file, a sub= sequent `opam update` will refresh the working copy from the remote source. >>=20 >> If you want to work with a local copy of that package, just do `opam pin= `. >>=20 >> If you want the bleeding edge version of a stable package, you can even = do `opam pin git://foo/bar`. >>=20 >> Quite the swiss-army knife, but each of those scenarios has come in usef= ul at one point or another, particularly when hacking on Mirage which requi= res rebuilding lots of forward dependencies if (e.g.) a network driver libr= ary is being modified. >>=20 >> -anil >>=20 >=20 > --=20 > 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