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 q29JnDpc019404 for ; Fri, 9 Mar 2012 20:49:13 +0100 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhMDABJeWk9KN1ZKlWdsb2JhbABChUKwHwEBAQEJCwkJEimCCgEBBAEjVgULCxoCGA4CAj0KEAYbh30FBKxyiieBL44zM2MEmxyNLQ X-IronPort-AV: E=Sophos;i="4.73,559,1325458800"; d="scan'208";a="135281029" Received: from mail6.webfaction.com (HELO smtp.webfaction.com) ([74.55.86.74]) by mail4-smtp-sop.national.inria.fr with ESMTP; 09 Mar 2012 20:49:07 +0100 Received: from heyho.local (53-234.197-178.cust.bluewin.ch [178.197.234.53]) by smtp.webfaction.com (Postfix) with ESMTP id BA7A3207B551; Fri, 9 Mar 2012 13:49:05 -0600 (CST) Date: Fri, 9 Mar 2012 20:49:03 +0100 From: =?utf-8?Q?Daniel_B=C3=BCnzli?= To: Sylvain Le Gall Cc: caml-list@inria.fr Message-ID: <3EEA65CD539D4607A565A85A85639F75@erratique.ch> In-Reply-To: References: <1991A512A37E49ACA5AAD30A38D628BF@erratique.ch> <1ACBE325A80144A4885B44685F6E9028@erratique.ch> <2588CBF13EAF449DBCAF86436DFC354E@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 q29JnDpc019404 Subject: Re: [Caml-list] Re: oasis packaging questions Le vendredi, 9 mars 2012 à 20:11, Sylvain Le Gall a écrit : > > > > Document "reference" > > Title: "Xmlm's documentation and module reference" > > Format: html > > Index: Xmlm.html > > Install: true > > DataFiles: doc/*.html, doc/*.css > > > > Document "distribution" > > Title: "Xmlm's distribution information files" > > Install: true > > DataFiles: README CHANGES > > > > Maybe a kind of enumerated Kind: field could give more information about the nature of the documents. That said, oasis still seems to be a little bit schizophrenic about installation: on one hand it shouldn't install, on the other hand it seems to offer fields to perform installation duties. > > I am probably off-topic, because I don't understand by what you mean > by "on one hand it shouldn't install, on the other hand it seems to > offer fields to perform installation duties." ? I was meaning in general. If oasis is supposed to be descriptive (in the sense here you have an executable, here you have a library, here you have documentation), why does it have a field like InstallDir for documents ? Why do we have something like XCustomInstall: cp XYZ; I mean understand why we have it, but shouldn't its usage be discouraged ? Now the Document sections I wrote above don't do anything for now but it seems to me that 1) It has the info for a potential downstream packager e.g. cp `oasis query Doc(reference)` $WHEREWEPUTTHATINOURDISTRIB 2) It has the info for the thing I choose to manage the oasis -install I hope that one day, that 2) will be able to its thing and push it at the right place (being it inside sitelib or not !). Isn't that a better approach than using XCustomInstall or InstallDir ? Should I do it differently ? Maybe the only thing that is missing in an agreement like you have for SourceRepository: this, head. to better caracterize the actual bits of documentation that are being described (b.t.w I added a Document samples with DataFiles:examples/*.ml) > But maybe what you miss here, > is that it is meant to build documentation. Yes, if eventually there's a system that is able to integerates these odocl why not. For now I don't see any advantage and I prefer to distribute them statically. One reason is that since all my documentation is in inside the .mlis I think its nice if someone just want to have a look at the docs that he doesn't need to build anything (e.g. if the lib has many deps). Best, Daniel