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 A51FD81792 for ; Mon, 8 Jul 2013 17:42:00 +0200 (CEST) Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of daniel.buenzli@erratique.ch) identity=pra; client-ip=74.55.86.74; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="daniel.buenzli@erratique.ch"; x-sender="daniel.buenzli@erratique.ch"; x-conformance=sidf_compatible Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of daniel.buenzli@erratique.ch) identity=mailfrom; client-ip=74.55.86.74; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="daniel.buenzli@erratique.ch"; x-sender="daniel.buenzli@erratique.ch"; x-conformance=sidf_compatible Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of postmaster@smtp.webfaction.com) identity=helo; client-ip=74.55.86.74; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="daniel.buenzli@erratique.ch"; x-sender="postmaster@smtp.webfaction.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AuIDAOrc2lFKN1ZKamdsb2JhbABagzsBg1S9XIEoDg0JDAYUKoIjAQEBAwEBAiBWBQsLGgImAgIoHxAGGxOHbgYECKdWkROBJo4SMweCVDNpA5UOg26EZxOONw X-IPAS-Result: AuIDAOrc2lFKN1ZKamdsb2JhbABagzsBg1S9XIEoDg0JDAYUKoIjAQEBAwEBAiBWBQsLGgImAgIoHxAGGxOHbgYECKdWkROBJo4SMweCVDNpA5UOg26EZxOONw X-IronPort-AV: E=Sophos;i="4.87,1020,1363129200"; d="scan'208";a="20384755" Received: from mail6.webfaction.com (HELO smtp.webfaction.com) ([74.55.86.74]) by mail3-smtp-sop.national.inria.fr with ESMTP; 08 Jul 2013 17:41:59 +0200 Received: from [192.168.1.126] (cpc3-cmbg9-0-0-cust324.5-4.cable.virginmedia.com [81.103.21.69]) by smtp.webfaction.com (Postfix) with ESMTP id 540F720FC8C5; Mon, 8 Jul 2013 15:41:57 +0000 (UTC) Date: Mon, 8 Jul 2013 16:41:55 +0100 From: =?utf-8?Q?Daniel_B=C3=BCnzli?= To: Thomas Gazagnaire Cc: Dagnat Fabien , "=?utf-8?Q?caml-list=40inria.fr?=" Message-ID: In-Reply-To: References: <8D4165F2-D097-4497-AD9F-18AFA1E21266@telecom-bretagne.eu> X-Mailer: sparrow 1.6.4 (build 1178) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: Re: [Caml-list] =?UTF-8?Q?man=2C_doc=2C_=E2=80=A6_and_opam?= Le lundi, 8 juillet 2013 =C3=A0 10:56, Thomas Gazagnaire a =C3=A9crit : > This is not totally true. ocamlfind also install all the C stubs in `DEST= DIR/stublibs/dllPKG.so` and this is not removed automatically by OPAM (as i= t currently has no good way to know the library name used by ocamlfind). So= , in this case, `ocamlfind remove PKG` does a bit more than removing DESTDI= R/PKG. Aha ok, spoke too fast.=20=20 > Indeed, no build system currently supports this. At one point, we've star= ted to discuss the integration with oasis, obuild and ocp-build (with Sylva= in, Vincent and Fabrice), but currenlty none of these systems has implement= ed that feature yet.=20=20 For myself, I do have simple requirements, my packages being mostly pure OC= aml. However I do need to scale horizontally, I have many packages develope= d, documented, maintained and formally released and I have an absolute *hat= e* for administrative duties. I now decided to eschew each of these solutions (tested all of them) as non= e in the current state is able to fullfill my needs in a satisfying way -- = both technically and from a usability point of view. For the curious see he= re [1] for how I plan to proceed from now on, at least until something *rea= lly* good emerges. However now that I decided to go the ocamlbuild only + install file route f= or pure ocaml packages it would be nice if there was a way for ocamlbuild t= o tell us, given an .mllib (or .itarget) file, all the installable artefact= s it *might* generate as it does actually have that knowledge and I'd prefe= r not to reencode it my scripts. I do it purely manually for now (see the l= inks from the message [1]) it's not too bad, but I'd prefer having a simple= r way so that I'm sure I don't miss anything (also if new build artefacts m= ay appear in the future like cmxs did).=20=20 =20=20 > The `.install` mechanics is not perfect yet (the file needs to be at the = root of the directory, and needs to be called PKG.install, where PKG is the= OPAM package name) but I've waited for feedback before improving this. As I said on opam-devel I don't think these requirements are that bad. Best, Daniel [1] http://lists.ocaml.org/pipermail/opam-devel/2013-July/000161.html