From: Thomas Gazagnaire <thomas@ocamlpro.com>
To: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
Cc: Philippe Veber <philippe.veber@gmail.com>,
Mirage List <cl-mirage@lists.cam.ac.uk>,
Alain Frisch <alain@frisch.fr>,
OCaml mailing-list <caml-list@inria.fr>,
Anil Madhavapeddy <anil@recoil.org>
Subject: Re: Opam package publication (was Re: [Caml-list] [ANN] beta-release of OPAM)
Date: Tue, 22 Jan 2013 16:48:33 +0000 [thread overview]
Message-ID: <B0679C48-0993-4D17-AF31-E7B2AC42B65A@ocamlpro.com> (raw)
In-Reply-To: <275158A520F84991A11398BE11E1CD8C@erratique.ch>
>> Homebrew use the concept of 'taps' where people can register alternative repositories, which will contain domain-specific packages (ocaml uses to have one before being integrated in the main repo). Doing that for OPAM is (I think) a bit overkill.
>
> Well to me it seems that opam already has the concept, tap = repo (or maybe I don't understand what a homebrew tap is).
Yes, that's pretty similar, but 'brew search' will also search into some pre-defined taps and you have predefined names for some of them. I just don't feel we need such tight integration in OPAM.
>> However, I'm happy to have a REPOSITORIES file at the root of OCamlPro/opam-repositories which lists the available repositories, and write a small script to automatically sync with these repo regularly. Feel free to add your repository in there, and I'll write the update script.
>
> Feels like a step in the right direction to me. But I don't think it's a good idea to make it fully automatic or at least something sensitive should be done to handle potential conflicts.
By automatic, I mean, we can have a script looking at the new packages available and create pull request for them in opam-repository (and we can continue to use the same workflow).
Thomas
next prev parent reply other threads:[~2013-01-22 16:48 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 [this message]
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=B0679C48-0993-4D17-AF31-E7B2AC42B65A@ocamlpro.com \
--to=thomas@ocamlpro.com \
--cc=alain@frisch.fr \
--cc=anil@recoil.org \
--cc=caml-list@inria.fr \
--cc=cl-mirage@lists.cam.ac.uk \
--cc=daniel.buenzli@erratique.ch \
--cc=philippe.veber@gmail.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