From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 12D797EEAF for ; Sat, 19 Jan 2013 11:41:14 +0100 (CET) Received-SPF: None (mail4-smtp-sop.national.inria.fr: no sender authenticity information available from domain of daniel.buenzli@erratique.ch) identity=pra; client-ip=74.55.86.74; receiver=mail4-smtp-sop.national.inria.fr; envelope-from="daniel.buenzli@erratique.ch"; x-sender="daniel.buenzli@erratique.ch"; x-conformance=sidf_compatible Received-SPF: None (mail4-smtp-sop.national.inria.fr: no sender authenticity information available from domain of daniel.buenzli@erratique.ch) identity=mailfrom; client-ip=74.55.86.74; receiver=mail4-smtp-sop.national.inria.fr; envelope-from="daniel.buenzli@erratique.ch"; x-sender="daniel.buenzli@erratique.ch"; x-conformance=sidf_compatible Received-SPF: None (mail4-smtp-sop.national.inria.fr: no sender authenticity information available from domain of postmaster@smtp.webfaction.com) identity=helo; client-ip=74.55.86.74; receiver=mail4-smtp-sop.national.inria.fr; envelope-from="daniel.buenzli@erratique.ch"; x-sender="postmaster@smtp.webfaction.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AkQDAPZ3+lBKN1ZKfmdsb2JhbABEhkW4Dw4BAQsJDAgUJ4IfAQUjVhALGgImAgJHEAYKEYgRBKo/kVeBI48DMmEDkloDiQcTjVQ X-IronPort-AV: E=Sophos;i="4.84,498,1355094000"; d="scan'208";a="169017440" Received: from mail6.webfaction.com (HELO smtp.webfaction.com) ([74.55.86.74]) by mail4-smtp-sop.national.inria.fr with ESMTP; 19 Jan 2013 11:41:00 +0100 Received: from [172.20.10.2] (109-234.197-178.cust.bluewin.ch [178.197.234.109]) by smtp.webfaction.com (Postfix) with ESMTP id EEB4266EFD2C; Sat, 19 Jan 2013 04:40:55 -0600 (CST) Date: Sat, 19 Jan 2013 11:40:52 +0100 From: =?utf-8?Q?Daniel_B=C3=BCnzli?= To: Philippe Veber Cc: Anil Madhavapeddy , Alain Frisch , Thomas Gazagnaire , OCaml mailing-list , Mirage List Message-ID: In-Reply-To: References: <6833F17C-B642-4ED9-8C8F-2665A9742845@ocamlpro.com> <50F831B6.6020404@frisch.fr> <224865B3-055C-4E03-AA42-9F962AD516D7@recoil.org> <50F92486.2020704@frisch.fr> <50F92FA9.8050707@frisch.fr> <28252449-E0B3-4A0E-A001-57B72712DD99@recoil.org> <4144589AC12E46C09674D6D80D984289@erratique.ch> X-Mailer: sparrow 1.6.4 (build 1178) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: Re: Opam package publication (was Re: [Caml-list] [ANN] beta-release of OPAM) Le samedi, 19 janvier 2013 =C3=A0 10:07, Philippe Veber a =C3=A9crit : > I hope I understood your point correctly, but you can already do that : i= f your repo is accessible via git, http or rsync protocols any user can use= it simultaneously with ocamlpro's. Yes, I know, that was not the point. I was proposing a lighter process for = a package to be included in opam's default repository.=20=20 As Alain mentioned, the current process is rather involved for package deve= lopers --- but I disagree with his idea of an upload web interface.=20=20 The idea is that package developers publish repos with their work and that = there's a kind of `import` or `copy` command in opam that allows to copy a = package from one repo to another (this could also be useful to make custom = repos). ocamlpro uses this command to transfer a package from the developer= 's repo to the default repo. This allows package users that are confident in a packager to use his repo = directly, and those that prefer to wait for the inclusion in opam default r= epo to wait for it while minimizing the overall energy spent for all the in= volved parties.=20=20 Best, Daniel