From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <alain@frisch.fr>
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 13D2D7EEAF
	for <caml-list@sympa.inria.fr>; Fri, 18 Jan 2013 12:19:05 +0100 (CET)
Received-SPF: None (mail4-smtp-sop.national.inria.fr: no sender
  authenticity information available from domain of
  alain@frisch.fr) identity=pra; client-ip=193.252.23.213;
  receiver=mail4-smtp-sop.national.inria.fr;
  envelope-from="alain@frisch.fr"; x-sender="alain@frisch.fr";
  x-conformance=sidf_compatible
Received-SPF: None (mail4-smtp-sop.national.inria.fr: no sender
  authenticity information available from domain of
  alain@frisch.fr) identity=mailfrom; client-ip=193.252.23.213;
  receiver=mail4-smtp-sop.national.inria.fr;
  envelope-from="alain@frisch.fr"; x-sender="alain@frisch.fr";
  x-conformance=sidf_compatible
Received-SPF: None (mail4-smtp-sop.national.inria.fr: no sender
  authenticity information available from domain of
  postmaster@msa.smtpout.orange.fr) identity=helo;
  client-ip=193.252.23.213;
  receiver=mail4-smtp-sop.national.inria.fr;
  envelope-from="alain@frisch.fr";
  x-sender="postmaster@msa.smtpout.orange.fr";
  x-conformance=sidf_compatible
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Au8AAJUu+VDB/BfVlGdsb2JhbABFvkwOAQEBAQkLCQkUAySCHgEBBThAARALGAkMCg8JAwIBAgFFBg0BBQIBAYgZvB6OBIM1A5YMhWuNVA
X-IronPort-AV: E=Sophos;i="4.84,491,1355094000"; 
   d="scan'208";a="168908875"
Received: from msa04.smtpout.orange.fr (HELO msa.smtpout.orange.fr) ([193.252.23.213])
  by mail4-smtp-sop.national.inria.fr with ESMTP; 18 Jan 2013 12:19:04 +0100
Received: from [192.168.1.105] ([90.44.19.86])
	by mwinf5d31 with ME
	id pPK31k00r1rRe5E03PK3KS; Fri, 18 Jan 2013 12:19:04 +0100
Message-ID: <50F92FA9.8050707@frisch.fr>
Date: Fri, 18 Jan 2013 12:19:05 +0100
From: Alain Frisch <alain@frisch.fr>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: Anil Madhavapeddy <anil@recoil.org>
CC: Thomas Gazagnaire <thomas@ocamlpro.com>, 
 OCaml mailing-list <caml-list@inria.fr>,
 Mirage List <cl-mirage@lists.cam.ac.uk>
References: <6833F17C-B642-4ED9-8C8F-2665A9742845@ocamlpro.com> <50F831B6.6020404@frisch.fr> <224865B3-055C-4E03-AA42-9F962AD516D7@recoil.org> <50F92486.2020704@frisch.fr> <DF5C351C-2B6D-4AA6-BCE7-3A9F0366CCCB@recoil.org>
In-Reply-To: <DF5C351C-2B6D-4AA6-BCE7-3A9F0366CCCB@recoil.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Caml-list] [ANN] beta-release of OPAM

On 01/18/2013 11:42 AM, Anil Madhavapeddy wrote:
> On 18 Jan 2013, at 10:31, Alain Frisch <alain@frisch.fr> wrote:
>> Shouldn't the package be called simply "trunk", without a reference to a version number?
>
> Yeah, but OPAM also has compiler version constraints, so that you can mark a package as requiring {>=4.00} for example.

Understood.

> $ mkdir -p my-repo/packages
> $ opam remote add localdev my-repo
> <create your package inside my-repo/packages/>
> $ opam update
> <the new packages will be available>
> $ opam install <new-package>

Thanks.  That's what I've done.

I've sent my first "pull request" for the inclusion of a new package in 
OPAM :-)


Are there plans to provide a more direct way to submit proposals for new 
packages?  If I understand correctly, the current scheme requires to 
create an account on github, fork the opam-repository, clone the fork 
locally, create and commit the package locally, push it to github, and 
then create a pull request.  Admittedly, this is not difficult once 
you're familiar with GIT and github, but I can imagine that it will 
still discourage some people from submitting their first package.  What 
about a simple web interface to upload a .tar.gz of the package 
description, for instance?  It should not be too hard to automate the 
treatment of uploaded package descriptions.

Alain