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 6A90C7F86A for ; Wed, 5 Mar 2014 16:11:36 +0100 (CET) Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of dra-news@metastack.com) identity=pra; client-ip=62.13.149.115; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="dra-news@metastack.com"; x-sender="dra-news@metastack.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of dra-news@metastack.com designates 62.13.149.115 as permitted sender) identity=mailfrom; client-ip=62.13.149.115; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="dra-news@metastack.com"; x-sender="dra-news@metastack.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of postmaster@outmail149115.authsmtp.co.uk) identity=helo; client-ip=62.13.149.115; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="dra-news@metastack.com"; x-sender="postmaster@outmail149115.authsmtp.co.uk"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AmoBAKE9F1M+DZVznGdsb2JhbABag0HCehYOAQEBAQEIFAk8giwIAh4STAUWUiMNAQ4BBB4Fh22eObAIkxAEjzKKPYknBIp7 X-IPAS-Result: AmoBAKE9F1M+DZVznGdsb2JhbABag0HCehYOAQEBAQEIFAk8giwIAh4STAUWUiMNAQ4BBB4Fh22eObAIkxAEjzKKPYknBIp7 X-IronPort-AV: E=Sophos;i="4.97,593,1389740400"; d="scan'208";a="51406734" Received: from outmail149115.authsmtp.co.uk ([62.13.149.115]) by mail3-smtp-sop.national.inria.fr with ESMTP; 05 Mar 2014 16:11:35 +0100 Received: from mail-c235.authsmtp.com (mail-c235.authsmtp.com [62.13.128.235]) by punt18.authsmtp.com (8.14.2/8.14.2/) with ESMTP id s25FBYU3086571 for ; Wed, 5 Mar 2014 15:11:34 GMT Received: from romulus.metastack.com (cpc1-cmbg5-0-0-cust241.5-4.cable.virginm.net [81.98.252.242]) (authenticated bits=0) by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id s25FBVOF077912 for ; Wed, 5 Mar 2014 15:11:31 GMT Received: from Altus ([31.88.167.57]) (authenticated bits=0) by romulus.metastack.com (8.14.2/8.14.2) with ESMTP id s25FBSu5000925 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Wed, 5 Mar 2014 15:11:30 GMT From: "David Allsopp" To: "OCaml List" Date: Wed, 5 Mar 2014 15:13:14 -0000 Organization: MetaStack Solutions Ltd. Message-ID: <000b01cf3885$6f1ef7a0$4d5ce6e0$@metastack.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: Ac84f3Jde4et/NjTTUiDzLaKkU9d4A== Content-Language: en-gb X-Scanned-By: MIMEDefang 2.65 on 172.16.0.20 X-Server-Quench: 6ede42c7-a478-11e3-b802-002590a15da7 X-AuthReport-Spam: If SPAM / abuse - report it at: http://www.authsmtp.com/abuse X-AuthRoute: OCd1ZAARAlZZVg1f DC4bFwdFRBksPQFF ChxFJgxfNlEAUAAU NkdBMnJSNkcdTBdX QSgLXkspAR9uW2N0 bxpQaA9cY0BNXkti UVZASkxQEQd2AxgD GRwbTRk8NAdDDgwW GjBiWXdSXUY0d0d6 QQBSQDlTYWUzb31O VEdQagJVJQBXLBdF aE1/VHEIaGVWZ380 FlAlByo2PzhUNGxV RRoRLFQdCUgMBHY6 Sg9KOh4mGElNXz80 LREtNkV0 X-Authentic-SMTP: 61633634383431.1023:706 X-AuthFastPath: 0 (Was 255) X-AuthSMTP-Origin: 81.98.252.242/25 X-AuthVirus-Status: No virus detected - but ensure you scan with your own anti-virus system. Subject: [Caml-list] Project hosting for new OCaml projects 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) * 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? Thanks! David