From: Alain Frisch <alain@frisch.fr>
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>
Subject: Re: [Caml-list] [ANN] beta-release of OPAM
Date: Fri, 18 Jan 2013 12:19:05 +0100 [thread overview]
Message-ID: <50F92FA9.8050707@frisch.fr> (raw)
In-Reply-To: <DF5C351C-2B6D-4AA6-BCE7-3A9F0366CCCB@recoil.org>
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
next prev parent reply other threads:[~2013-01-18 11:19 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 15:40 Thomas Gazagnaire
2013-01-15 15:42 ` [Caml-list] " Anil Madhavapeddy
2013-01-15 16:17 ` Thomas Gazagnaire
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 [this message]
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=50F92FA9.8050707@frisch.fr \
--to=alain@frisch.fr \
--cc=anil@recoil.org \
--cc=caml-list@inria.fr \
--cc=cl-mirage@lists.cam.ac.uk \
--cc=thomas@ocamlpro.com \
/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