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 mail4-relais-sop.national.inria.fr (mail4-relais-sop.national.inria.fr [192.134.164.105]) by sympa.inria.fr (Postfix) with ESMTPS id 185B57EEAF for ; Tue, 15 Jan 2013 17:17:52 +0100 (CET) Received-SPF: None (mail4-smtp-sop.national.inria.fr: no sender authenticity information available from domain of thomas.gazagnaire@gmail.com) identity=pra; client-ip=209.85.212.175; receiver=mail4-smtp-sop.national.inria.fr; envelope-from="thomas.gazagnaire@gmail.com"; x-sender="thomas.gazagnaire@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail4-smtp-sop.national.inria.fr: domain of thomas.gazagnaire@gmail.com designates 209.85.212.175 as permitted sender) identity=mailfrom; client-ip=209.85.212.175; receiver=mail4-smtp-sop.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 (mail4-smtp-sop.national.inria.fr: no sender authenticity information available from domain of postmaster@mail-wi0-f175.google.com) identity=helo; client-ip=209.85.212.175; receiver=mail4-smtp-sop.national.inria.fr; envelope-from="thomas.gazagnaire@gmail.com"; x-sender="postmaster@mail-wi0-f175.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AggCAEV+9VDRVdSvjWdsb2JhbABFgy66VRYOAQEBAQkJCwkSBiOCHgEBAwEBOgYBKw0BAwELAQUFBxEuNAEFARwGExSHcwMJBgyaU44kgQqFPScNhzUBBQyMaYNiYQOXKIRPiH0/gViCPw X-IronPort-AV: E=Sophos;i="4.84,473,1355094000"; d="scan'208";a="168554901" Received: from mail-wi0-f175.google.com ([209.85.212.175]) by mail4-smtp-sop.national.inria.fr with ESMTP/TLS/RC4-SHA; 15 Jan 2013 17:17:51 +0100 Received: by mail-wi0-f175.google.com with SMTP id hm11so2500019wib.8 for ; Tue, 15 Jan 2013 08:17:51 -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=EnQgdEKzmou4/jRD6GZVAW+XzYD/+cxFg0C8BCWEZ6o=; b=asfK19xzqLenh/BlZg6MCZfgSJeLXdcjdaqGrhtZsOgBVV7reJbEZgC+E2QrjzQit3 hIu20n/eFU7DSLUf2EzHmw+GWMqbKNp0N/nj2oXIG9Rliwz2+aq0YoGqYWUqAGMJMLcg hwIQWiL1qy3l8G7lnbMqrdLmSXYVPKCqB+9kOC0oZt1ucvX8VDE1VNHfMgdKIy82uiZe B6+RJP4wO0TenzO6mOuNlFfs3b0+ZDsm/EfxVqI7ihocbdMvc2+bgw1g0MCak9Bkq4K0 1nOqltyiN1II6Sz84bCoqN31CajiW6GYNtXQJaRrZJzI7b6A3un8nxkdxoa2y1OetCvS AagA== X-Received: by 10.194.80.73 with SMTP id p9mr42013011wjx.4.1358266671115; Tue, 15 Jan 2013 08:17:51 -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 fv2sm4071218wib.4.2013.01.15.08.17.49 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 15 Jan 2013 08:17:50 -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: Date: Tue, 15 Jan 2013 16:17:49 +0000 Cc: OCaml mailing-list , Mirage List Content-Transfer-Encoding: quoted-printable Message-Id: <3764589D-EC12-4CD5-A76F-A009BE2DDE8E@ocamlpro.com> References: <6833F17C-B642-4ED9-8C8F-2665A9742845@ocamlpro.com> To: Anil Madhavapeddy X-Mailer: Apple Mail (2.1085) Subject: [Caml-list] Re: [ANN] beta-release of OPAM To people already using OPAM, I forgot to mention that it is highly recomme= nded to NOT upgrade opam using opam. The auto-update thing was a mistake at= the first place. It is also advised to start from a fresh opam init. It sh= ould work if you don't, but it would definitely avoid some confusions in so= me corner-cases. -- Thomas On Jan 15, 2013, at 3:42 PM, Anil Madhavapeddy wrote: > If you're using Homebrew on the Mac, just do a "brew update" and you shou= ld get the latest beta release (0.9.1) via it. Enjoy! >=20 > -anil >=20 > On 15 Jan 2013, at 15:40, Thomas Gazagnaire wrote: >=20 >> I'm very happy to announce the beta release of OPAM (0.9.1). OPAM is a p= ackage manager for OCaml to install libraries and tools from source archive= s. It supports multiple simultaneous compiler installations, flexible packa= ge constraints, and a Git-friendly development workflow. >>=20 >> The goal of this beta release is to formally introduce OPAM to the commu= nity, to gather some general feedback on the documentation and tools and do= uble-check that we've not forgotten some useful features. I would also like= to use that opportunity to make an official call to maintainers: if you ha= ve developed packages which are already in OPAM do not hesitate to claim th= eir ownership and to improve their description - if your packages are not y= et in, it's time to start packaging them!=20 >>=20 >> OPAM is developed by OCamlPro[1] and has been in alpha release since Jun= e 2012. It is already quite mature and has gained some nice momentum (+40 c= ontributors, +300 packages). OPAM has been initially funded by Jane Street= [2] and the DORM EU research project, and it has received continuous help a= nd resources from OCamlLabs[3]. >>=20 >> The source code of OPAM is available on Github: >> * installer: https://github.com/OCamlpro/opam >> * packages and compiler descriptions: https://github.com/OCamlPro/opam-r= epository >> * website: https://github.com/OCamlPro/opam2web >>=20 >> The documention: >> * install instructions and tutorial are available http://opam.ocamlpro.c= om/ >> * the main source of documentation is 'opam --help' or 'opam -= -help' >> * user manual: https://github.com/OCamlPro/opam/raw/master/doc/dev-manua= l/dev-manual.pdf >>=20 >> You can report issues on github bug tracker: >> * https://github.com/OCamlPro/opam/issues >>=20 >> The next steps for us is to focus on improving the package descriptions = quality and the global consistency of https://github.com/OCamlPro/opam-repo= sitory. We will gladly accept any kind of help and support from the communi= ty to do this! We plan to announce the release of 1.0.0 in a couple of mon= ths, with improved package quality and better integration with the future O= Caml platform. >>=20 >> Last point, if you are working in a company and that you already use OPA= M, or plan to use OPAM, and you would like to help us ensuring it a sustain= able future[2], you can contact us at contact@ocamlpro.com.=20 >>=20 >> On behalf of the OPAM team, >> Thomas Gazagnaire >>=20 >> [1] http://www.ocamlpro.com/ >> [2] http://www.janestreet.com/ >> [3] http://www.cl.cam.ac.uk/projects/ocamllabs/ >>=20 >>=20 >>=20 >=20