From: Thomas Gazagnaire <thomas@ocamlpro.com>
To: Anil Madhavapeddy <anil@recoil.org>
Cc: OCaml mailing-list <caml-list@inria.fr>,
Mirage List <cl-mirage@lists.cam.ac.uk>
Subject: [Caml-list] Re: [ANN] beta-release of OPAM
Date: Tue, 15 Jan 2013 16:17:49 +0000 [thread overview]
Message-ID: <3764589D-EC12-4CD5-A76F-A009BE2DDE8E@ocamlpro.com> (raw)
In-Reply-To: <A50624F5-9601-492C-84E1-D2D54081AB0E@recoil.org>
To people already using OPAM, I forgot to mention that it is highly recommended 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 should work if you don't, but it would definitely avoid some confusions in some 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 should get the latest beta release (0.9.1) via it. Enjoy!
>
> -anil
>
> On 15 Jan 2013, at 15:40, Thomas Gazagnaire <thomas@ocamlpro.com> wrote:
>
>> I'm very happy to announce the beta release of OPAM (0.9.1). OPAM is a package manager for OCaml to install libraries and tools from source archives. It supports multiple simultaneous compiler installations, flexible package constraints, and a Git-friendly development workflow.
>>
>> The goal of this beta release is to formally introduce OPAM to the community, to gather some general feedback on the documentation and tools and double-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 have developed packages which are already in OPAM do not hesitate to claim their ownership and to improve their description - if your packages are not yet in, it's time to start packaging them!
>>
>> OPAM is developed by OCamlPro[1] and has been in alpha release since June 2012. It is already quite mature and has gained some nice momentum (+40 contributors, +300 packages). OPAM has been initially funded by Jane Street[2] and the DORM EU research project, and it has received continuous help and resources from OCamlLabs[3].
>>
>> The source code of OPAM is available on Github:
>> * installer: https://github.com/OCamlpro/opam
>> * packages and compiler descriptions: https://github.com/OCamlPro/opam-repository
>> * website: https://github.com/OCamlPro/opam2web
>>
>> The documention:
>> * install instructions and tutorial are available http://opam.ocamlpro.com/
>> * the main source of documentation is 'opam --help' or 'opam <command> --help'
>> * user manual: https://github.com/OCamlPro/opam/raw/master/doc/dev-manual/dev-manual.pdf
>>
>> You can report issues on github bug tracker:
>> * https://github.com/OCamlPro/opam/issues
>>
>> The next steps for us is to focus on improving the package descriptions quality and the global consistency of https://github.com/OCamlPro/opam-repository. We will gladly accept any kind of help and support from the community to do this! We plan to announce the release of 1.0.0 in a couple of months, with improved package quality and better integration with the future OCaml platform.
>>
>> Last point, if you are working in a company and that you already use OPAM, or plan to use OPAM, and you would like to help us ensuring it a sustainable future[2], you can contact us at contact@ocamlpro.com.
>>
>> On behalf of the OPAM team,
>> Thomas Gazagnaire
>>
>> [1] http://www.ocamlpro.com/
>> [2] http://www.janestreet.com/
>> [3] http://www.cl.cam.ac.uk/projects/ocamllabs/
>>
>>
>>
>
next prev parent reply other threads:[~2013-01-15 16:17 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 15:40 [Caml-list] " Thomas Gazagnaire
2013-01-15 15:42 ` [Caml-list] " Anil Madhavapeddy
2013-01-15 16:17 ` Thomas Gazagnaire [this message]
2013-01-15 19:18 ` Alan Schmitt
2013-01-15 19:25 ` Fabrice Le Fessant
2013-01-15 19:29 ` Anil Madhavapeddy
2013-01-15 19:45 ` Roberto Di Cosmo
2013-01-15 21:12 ` Wojciech Meyer
2013-01-16 10:01 ` [Caml-list] " Anil Madhavapeddy
2013-01-16 10:08 ` Wojciech Meyer
2013-01-16 12:13 ` Gabriel Scherer
2013-01-16 14:43 ` Wojciech Meyer
2013-01-16 14:50 ` Gabriel Scherer
2013-01-16 17:27 ` Fabrice Le Fessant
2013-01-16 17:40 ` Thomas Gazagnaire
2013-01-16 17:46 ` Fabrice Le Fessant
2013-01-16 20:22 ` Roberto Di Cosmo
2013-01-15 20:02 ` [Caml-list] " Daniel Bünzli
2013-01-15 22:16 ` Thomas Gazagnaire
2013-01-15 17:45 ` [Caml-list] " Daniel Bünzli
2013-01-17 7:52 ` [Caml-list] " Sylvain Le Gall
2013-01-16 16:54 ` [Caml-list] " Mike Lin
2013-01-16 17:29 ` Daniel Bünzli
2013-01-17 17:15 ` Alain Frisch
2013-01-17 17:22 ` Anil Madhavapeddy
2013-01-18 10:31 ` Alain Frisch
2013-01-18 10:42 ` Anil Madhavapeddy
2013-01-18 10:46 ` Fabrice Le Fessant
2013-01-22 15:57 ` Thomas Gazagnaire
2013-01-18 11:19 ` Alain Frisch
2013-01-18 11:27 ` Anil Madhavapeddy
2013-01-18 16:23 ` Opam package publication (was Re: [Caml-list] [ANN] beta-release of OPAM) Daniel Bünzli
2013-01-19 9:07 ` Philippe Veber
2013-01-19 10:40 ` Daniel Bünzli
2013-01-22 15:46 ` Thomas Gazagnaire
2013-01-22 16:23 ` Daniel Bünzli
2013-01-22 16:48 ` Thomas Gazagnaire
2013-01-22 17:05 ` Daniel Bünzli
2013-01-22 16:35 ` Alain Frisch
2013-01-22 16:50 ` Fabrice Le Fessant
2013-01-22 16:53 ` Thomas Gazagnaire
2013-01-22 16:59 ` Daniel Bünzli
2013-01-22 18:03 ` Anil Madhavapeddy
2013-01-17 19:33 ` [Caml-list] Re: [ANN] beta-release of OPAM Hongbo Zhang
2013-01-18 12:18 ` [Caml-list] " aditya siram
2013-01-18 18:23 ` Thomas Gazagnaire
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3764589D-EC12-4CD5-A76F-A009BE2DDE8E@ocamlpro.com \
--to=thomas@ocamlpro.com \
--cc=anil@recoil.org \
--cc=caml-list@inria.fr \
--cc=cl-mirage@lists.cam.ac.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox