From: Fabrice Le Fessant <fabrissimo@gmail.com>
To: caml-list@inria.fr
Subject: Re: Opam package publication (was Re: [Caml-list] [ANN] beta-release of OPAM)
Date: Tue, 22 Jan 2013 17:50:47 +0100 [thread overview]
Message-ID: <50FEC367.7000204@gmail.com> (raw)
In-Reply-To: <50FEBFD4.9080004@frisch.fr>
On 01/22/2013 05:35 PM, Alain Frisch wrote:
> What's the benefit of the git/github submission workflow? I don't
> immediately see how this is easier for people responsible of
> accepting/rejection packages than, say, something based on an upload
> interface (or even simpler, an email with an attachment).
I think one advantage of the github submission workflow is that
everybody can comment on a pull-request, ask for modifications, until
the patch seems ok for acceptance.
I "opamised" the unstable branch of TypeRex this week (mostly to provide
access to the new version of ocp-build, not for the editor that is not
ready), and I wrote a simple program "ocp-opamer" to simplify the
workflow (it is installed with TypeRex 1.99.1-beta) :
1/ you fork the opam-repository on GitHub
2/ for your package "foobar", you call:
ocp-opamer -login your-github-login -opam foobar.opam -descr
foobar.descr foobar 1.2.3 http://an.url.for/the.tarball.tgz
It will checkout your opam-repository, create the sub-directory and the
'url' file with the md5sum after downloading archive, and upload a new
branch 'foobar' to your repository.
3/ from your repository, you send a pull-request to the main rep, for
branch 'foobar'
Does it sound so complex ? For TypeRex, step (2) is a rule in the
Makefile, step (1) has to be done once, and (3) is quite simple...
If you think the tool is worth it, it could be added to an "opam-tools"
package in the future...
--Fabrice
next prev parent reply other threads:[~2013-01-22 16:50 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 15:40 [Caml-list] [ANN] beta-release of OPAM 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
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 [this message]
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=50FEC367.7000204@gmail.com \
--to=fabrissimo@gmail.com \
--cc=caml-list@inria.fr \
/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).