From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on yquem.inria.fr X-Spam-Level: X-Spam-Status: No, score=0.1 required=5.0 tests=AWL autolearn=disabled version=3.1.3 Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by yquem.inria.fr (Postfix) with ESMTP id 38F2EBC6C for ; Fri, 1 Feb 2008 13:36:31 +0100 (CET) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ao8CAAihokdYvxGE/2dsb2JhbACuDw X-IronPort-AV: E=Sophos;i="4.25,290,1199660400"; d="scan'208";a="6816085" Received: from www.rastageeks.org (HELO mail.rastageeks.org) ([88.191.17.132]) by mail2-smtp-roc.national.inria.fr with ESMTP; 01 Feb 2008 13:36:31 +0100 Received: from [192.168.112.144] (sphinx.lix.polytechnique.fr [129.104.11.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.rastageeks.org (Postfix) with ESMTP id 54AF39CFCB for ; Fri, 1 Feb 2008 13:36:10 +0100 (CET) From: Romain Beauxis To: caml-list@yquem.inria.fr Subject: Ocamlcore.org: Discussions place, and requirements Date: Fri, 1 Feb 2008 13:36:09 +0100 User-Agent: KMail/1.9.7 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200802011336.09562.toots@rastageeks.org> X-Spam: no; 0.00; ocaml:01 ocaml:01 cpan:01 parser:01 ocamlfind:01 ocamlfind:01 tarball:01 bindings:01 modules:02 modules:02 module:03 module:03 debian:04 upstream:04 perhaps:05 Hi all ! I have two question related to the recent discussions around ocaml community. First of all, I'd like to know if we should continu discussing here, or we better switch to a new mailing list. There's a mailman almost ready on ocamlcore.org, so perhaps it should be better to continue on a mailing list there ? Second questions is ocaml modules that we are going to distribute there. While we have discussed that different way we could use to collect projects from different places, I don't think we discussed the minimal support that the module should provide when it comes to installing and registering the module. For instance, all perl modules on CPAN share a common build and install system, the same for PHP pear and etc.. This can be a real trouble sometimes, like for the xml-light parser: while it does not support ocamlfind, the debian package added it, which I think is fine. But, our configure script detects xml-light based on ocamlfind, so it is screwed up when users want to build the software but installed xml-ligth from upstream tarball... I would recommend that we agreee on a minimal support the a module should ship to be part of ocamlcore.org. My point would be that it should provide a META file that should work with ocamlfind. Others might have a better idea, but it would be nice to choose something, don't you think ? Then, we should also provide templates for doing so. We have templates for configure+ocamlfind which works for all our bindings... Romain