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 mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by sympa.inria.fr (Postfix) with ESMTPS id BD3277F860 for ; Thu, 6 Mar 2014 01:21:19 +0100 (CET) Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of sylvain@le-gall.net) identity=pra; client-ip=80.91.229.3; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="gclci-caml-list@m.gmane.org"; x-sender="sylvain@le-gall.net"; x-conformance=sidf_compatible Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of gclci-caml-list@m.gmane.org designates 80.91.229.3 as permitted sender) identity=mailfrom; client-ip=80.91.229.3; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="gclci-caml-list@m.gmane.org"; x-sender="gclci-caml-list@m.gmane.org"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of postmaster@plane.gmane.org designates 80.91.229.3 as permitted sender) identity=helo; client-ip=80.91.229.3; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="gclci-caml-list@m.gmane.org"; x-sender="postmaster@plane.gmane.org"; x-conformance=sidf_compatible; x-record-type="v=spf1" X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AtYDAEq/F1NQW+UDb2dsb2JhbABag0HCfxYOAQwLCgYWKIIlAQEBBIEJCxIGLhAsDQENGRqHYwHPDI5uhCIEmW+JJwSJDYFu X-IPAS-Result: AtYDAEq/F1NQW+UDb2dsb2JhbABag0HCfxYOAQwLCgYWKIIlAQEBBIEJCxIGLhAsDQENGRqHYwHPDI5uhCIEmW+JJwSJDYFu X-IronPort-AV: E=Sophos;i="4.97,596,1389740400"; d="scan'208";a="51450453" Received: from plane.gmane.org ([80.91.229.3]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/AES256-SHA; 06 Mar 2014 01:20:55 +0100 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1WLM3N-0002Am-Ly for caml-list@inria.fr; Thu, 06 Mar 2014 01:20:49 +0100 Received: from root.ovh.le-gall.net ([37.59.37.175]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 06 Mar 2014 01:20:49 +0100 Received: from sylvain by root.ovh.le-gall.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 06 Mar 2014 01:20:49 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: caml-list@inria.fr From: Sylvain Le Gall Date: Thu, 6 Mar 2014 00:20:24 +0000 (UTC) Message-ID: References: <000b01cf3885$6f1ef7a0$4d5ce6e0$@metastack.com> X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: root.ovh.le-gall.net User-Agent: slrn/pre1.0.0-18 (Linux) Subject: Re: [Caml-list] Project hosting for new OCaml projects On 05-03-2014, David Allsopp wrote: > I've got a bit of code in a library which seems worth putting online. I'm > trying to consolidate the steps that should be taken to accomplish that > (beyond simply putting a tarball online!) and wondering if anyone can > confirm if what I've come up with is the "best/obvious" course of action. > Indeed, are there already "idiot"'s guides for this - I couldn't see > anything like it on ocaml.org et al? > > So, this particular library is a pure OCaml library, which simplifies things > somewhat. At present it's built using GNU make and of course it is managed > using findlib. > > It seems that the following are worth doing: > > * Support OASIS (and in so doing, I believe that will migrate its build > system to ocamlbuild) Esp. for pure OCaml libraries, OASIS will provide you with all you need to generate in one step (e.g. .cmxs, .cmxa on the right arch and not on the other, automatic generation of your META files with the right dependencies and version and so on and so forth). Although if you have a working makefile, that you install .cmxa only on the right architecture (amd64, i386 and no mips) you should be fine and won't have to use OASIS. I am biased here, but OASIS helps me to lower the TCO of 24+ libraries/program with an easy workflow for quick releases (but I am an OASIS poweruser and probably have access to advanced tools that uses OASIS). > * Support OPAM (which looks incredibly straightforward - being primarily a > Windows user, the OPAM typhoon has flowed past me thus far) > * Put the SCM online somewhere; submit a pull request for opam-repository; > announce it > > So, apart from any obvious errors/omissions in those steps, I have two > questions: > > 1. What are the differences, politely, in terms of things you can and can't > do between using GitHub and the OCaml Forge for the project pages? The Forge > seems the obvious choice, even ignoring the offensive name of the other! > 2. Given that, is there any benefit/different to hosting the git repository > on the Forge vs hosting it on github and simply linking to it from the > Forge? If you plan to have contribution and want to manage them: GitHub. For big projects, for which I am expecting contributions, I use GitHub and the OCaml Forge to distribute tarballs and maintain web pages of the project. For smaller project, I only use the OCaml Forge. Cheers, Sylvain Le Gall -- Website: http://sylvain.le-gall.net/ OCaml forge: http://forge.ocamlcore.org OCaml blogs: http://planet.ocaml.org