From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail4-relais-sop.national.inria.fr (mail4-relais-sop.national.inria.fr [192.134.164.105]) by walapai.inria.fr (8.13.6/8.13.6) with ESMTP id q28KxPZ0003666 for ; Thu, 8 Mar 2012 21:59:30 +0100 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AuYDAM8cWU9KN1ZKlWdsb2JhbABDhF9WsBYBAQEBCQsJCRIpggoBAQQBDBdWBQsJAhoCGA4CAj0KEAYbhgmBdAUEqCeSG4EvjhEzYwSbF40qgVs X-IronPort-AV: E=Sophos;i="4.73,553,1325458800"; d="scan'208";a="135104465" Received: from mail6.webfaction.com (HELO smtp.webfaction.com) ([74.55.86.74]) by mail4-smtp-sop.national.inria.fr with ESMTP; 08 Mar 2012 21:59:29 +0100 Received: from heyho.local (53-234.197-178.cust.bluewin.ch [178.197.234.53]) by smtp.webfaction.com (Postfix) with ESMTP id 4108626ECAE5; Thu, 8 Mar 2012 14:59:27 -0600 (CST) Date: Thu, 8 Mar 2012 21:59:23 +0100 From: =?utf-8?Q?Daniel_B=C3=BCnzli?= To: Sylvain Le Gall Cc: caml-list@inria.fr Message-ID: <1ACBE325A80144A4885B44685F6E9028@erratique.ch> In-Reply-To: References: <1991A512A37E49ACA5AAD30A38D628BF@erratique.ch> X-Mailer: sparrow 1.5 (build 1043.1) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by walapai.inria.fr id q28KxPZ0003666 Subject: Re: [Caml-list] Re: oasis packaging questions > I don't think I'll be able to integrate the Object section in 0.3. I > am really planning to release it soon. For me you can forget about it. Jérémie convinced me that even for single module libraries cma is better (see discussion on list). > I just had a quick look at your > git repository and I don't think there will be a difference for user > if it is a .cma (as long as they use ocamlfind). I also think so. > Never try autoconf ;-) Never did ! Always scared me away. > OK, so first of all you are talking about the odb/GODI/oasis-db level. > OASIS itself is not meant to handle that directly. There will be a > plugin "oasis-db" that will allow you to do "oasis install xmlm" and > "oasis uninstalll xmlm" and fetch the source from > http://oasis.ocamlcore.org but this is the future and this won't be > the core oasis system. You can have a look at odb that allow you to > already do that after having uploaded your package to > http://oasis.ocamlcore.org. > > Concerning the ocamlfind install + documentation. I understand you but > it is technically not feasible right now (AFAIK). Simple fact: > ocamlfind cannot install files in subdirectories. Ok interesting fact. This raises a few comments/questions. 1) You tell me that's none of oasis business. But setup.ml sports a -install option so you actually deal with installing things (even if its via ocamlfind). More than that the examples I saw for Document sections are along the lines of copying things to a specific $htmldir so oasis seems to deal with that... At least that's the place where *something* should happen so that the right info gets to the right place. 2) How does godi et al. handle documentation ? I know for sure that odb doesn't do anything about it. 3) Would ocamlfind consider extending its approach to be able to install files in subdirectories ? I really think that easy access to README, CHANGES and other bits like ocamldoc generated doc is paramount in a good package system since you don't get to see the tarballs anymore. I try to do my best and spend long hours on the documentation of the things I distribute (doesn't mean it's perfect, I sometimes don't understand what I wrote myself...), I want them to be somehow easily accessible (and easily destroyable). Can't we agree on something at that level ? Best, Daniel P.S. Btw. setup.ml -install should maybe also install the _oasis files.