caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Anil Madhavapeddy <anil@recoil.org>
To: Malcolm Matalka <mmatalka@gmail.com>
Cc: Thomas Gazagnaire <thomas@gazagnaire.org>,
	Ocaml Mailing List <caml-list@inria.fr>,
	Louis Gesbert <louis.gesbert@ocamlpro.com>
Subject: Re: [Caml-list] [ANN] final release of OPAM 1.1.0
Date: Thu, 26 Dec 2013 20:54:53 +0000	[thread overview]
Message-ID: <193AB6FA-27C5-4208-8F25-23589902F705@recoil.org> (raw)
In-Reply-To: <87d2kl3x28.fsf@gmail.com>

It probably should have been 2.0.0, but it was too late in the release
cycle before we gave up on 1.0 compatibility.  Upgrades never work for
the first release anyway :-)

Thanks for the Nix package, I'm looking forward to trying it out!
(and a belated thank you to Mehdi Dogguy for upload OPAM 1.1 to Debian
testing as well).

-anil

On 25 Dec 2013, at 13:00, Malcolm Matalka <mmatalka@gmail.com> wrote:

> Out of curiosity, since this opam 1.1.0 is not backwards compatible with
> 1.0.0, why is it not opam 2.0.0?
> 
> /Malcolm
> 
> Thomas Gazagnaire <thomas@gazagnaire.org> writes:
> 
>> After a while staged as RC, we are proud to announce the final release of OPAM 1.1.0 !
>> 
>> Thanks again to those who have helped testing and fixing the last few issues.
>> 
>> 
>> == Important note ==
>> 
>> The repository format has been improved with incompatible new features ; to
>> account for this, the _new_ repository is now hosted at opam.ocaml.org, and
>> the legacy repository at opam.ocamlpro.com is kept to support OPAM 
>> 1.0 installations, but is unlikely to benefit from many package updates.
>> Migration to opam.ocaml.org will be done automatically as soon as you upgrade
>> your OPAM version.
>> 
>> You're still free, of course, to use any third-party repositories instead or in addition.
>> 
>> 
>> == Installing ==
>> 
>> NOTE: When switching from 1.0, the internal state will need to be upgraded.
>> THIS PROCESS CANNOT BE REVERTED. We have tried hard to make it fault-
>> resistant, but failures might happen. In case you have precious data in your 
>> ~/.opam folder, it is advised to backup that folder before you upgrade to 
>> 1.1.0.
>> 
>> Using the binary installer:
>> - download and run http://www.ocamlpro.com/pub/opam_installer.sh
>> 
>> Using the .deb packages from Anil's PPA (binaries are currently synching, see [1]):
>>    add-apt-repository ppa:avsm/ppa
>>    apt-get update
>>    sudo apt-get install opam
>> 
>> For OSX users, the homebrew package will be updated shortly.
>> 
>> or build it from sources at :
>> - http://www.ocamlpro.com/pub/opam-full-1.1.0.tar.gz
>> - https://github.com/ocaml/opam/releases/tag/1.1.0
>> 
>> == For those who haven't been paying attention ==
>> 
>> OPAM is a source-based package manager for OCaml. It supports multiple
>> simultaneous compiler installations, flexible package constraints, and
>> a Git-friendly development workflow. OPAM is edited and
>> maintained by OCamlPro, with continuous support from OCamlLabs and the
>> community at large (including its main industrial users such as
>> Jane-Street and Citrix).
>> 
>> The "official" package repository is now hosted at https://opam.ocaml.org, synchronised with the
>> Git repository at http://github.com/ocaml/opam-repository, where you can contribute new packages
>> descriptions. Those are under a CC0 license, a.k.a. public domain, to ensure they will always
>> belong to the community.
>> 
>> Thanks to all of you who have helped build this repository and made OPAM such a success.
>> 
>> 
>> == Changes ==
>> 
>> Too many to list here, see
>> https://raw.github.com/OCamlPro/opam/1.1.0/CHANGES
>> 
>> For packagers, some new fields have appeared in the OPAM description format:
>> - `depexts` provides facilities for dealing with system (non ocaml) dependencies
>> - `messages`, `post-messages` can be used to notify the user eg. of licensing information,
>>  or help her  troobleshoot at package installation.
>> - `available` supersedes `ocaml-version` and `os` constraints, and can contain
>>  more expressive formulas
>> 
>> Also, we have integrated the main package repository with Travis, which will help us 
>> to improve the quality of contributions (see [2]).
>> 
>> 
>> Enjoy !
>> 
>> Thomas,  Louis and all the OPAM team
>> 
>> [1] https://launchpad.net/~avsm/+archive/ppa/+builds?build_state=pending
>> [2] http://anil.recoil.org/2013/09/30/travis-and-ocaml.html
> 
> -- 
> 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
> 


      reply	other threads:[~2013-12-26 20:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-08 15:35 Thomas Gazagnaire
2013-11-08 15:46 ` Anil Madhavapeddy
2013-12-17 22:35 ` Malcolm Matalka
2013-12-25 13:00 ` Malcolm Matalka
2013-12-26 20:54   ` Anil Madhavapeddy [this message]

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=193AB6FA-27C5-4208-8F25-23589902F705@recoil.org \
    --to=anil@recoil.org \
    --cc=caml-list@inria.fr \
    --cc=louis.gesbert@ocamlpro.com \
    --cc=mmatalka@gmail.com \
    --cc=thomas@gazagnaire.org \
    /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;
as well as URLs for NNTP newsgroup(s).