From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id 053A97FCCB for ; Mon, 27 Apr 2015 13:55:47 +0200 (CEST) Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of francois.bobot@cea.fr) identity=pra; client-ip=132.167.192.142; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="francois.bobot@cea.fr"; x-sender="francois.bobot@cea.fr"; x-conformance=sidf_compatible Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of francois.bobot@cea.fr) identity=mailfrom; client-ip=132.167.192.142; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="francois.bobot@cea.fr"; x-sender="francois.bobot@cea.fr"; x-conformance=sidf_compatible Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@cirse-out.extra.cea.fr) identity=helo; client-ip=132.167.192.142; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="francois.bobot@cea.fr"; x-sender="postmaster@cirse-out.extra.cea.fr"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A0BsAQC+Ij5VnI7Ap4Rch1XIJoJdAoEwPBABAQEBAQEBEQEBAQEBCAsJCSEuhCABAQEDASMPAQVAAQULCw4KAgIFFgsCAgkDAgECAUUGDQEHAheFYIIoCLIPk1UBAQEBAQUBAQEBAQEBARqBIYkVgQKFBQeCaIFFAQSPM5QUjiiCCIIRgzEBAQE X-IPAS-Result: A0BsAQC+Ij5VnI7Ap4Rch1XIJoJdAoEwPBABAQEBAQEBEQEBAQEBCAsJCSEuhCABAQEDASMPAQVAAQULCw4KAgIFFgsCAgkDAgECAUUGDQEHAheFYIIoCLIPk1UBAQEBAQUBAQEBAQEBARqBIYkVgQKFBQeCaIFFAQSPM5QUjiiCCIIRgzEBAQE X-IronPort-AV: E=Sophos;i="5.11,656,1422918000"; d="scan'208";a="137753915" Received: from cirse-out.extra.cea.fr ([132.167.192.142]) by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/DHE-RSA-AES256-SHA; 27 Apr 2015 13:55:46 +0200 Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t3RBtjVG031035; Mon, 27 Apr 2015 13:55:45 +0200 Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id C553B204B3A; Mon, 27 Apr 2015 13:57:17 +0200 (CEST) Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id B8752204A6A; Mon, 27 Apr 2015 13:57:17 +0200 (CEST) Received: from [10.8.32.80] (is222783.intra.cea.fr [10.8.32.80]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t3RBtjbr016577; Mon, 27 Apr 2015 13:55:45 +0200 Message-ID: <553E23C1.1000802@cea.fr> Date: Mon, 27 Apr 2015 13:55:45 +0200 From: =?UTF-8?B?RnJhbsOnb2lzIEJvYm90?= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.6.0 MIME-Version: 1.0 To: Gerd Stolpmann CC: OCaml Mailing List References: <54F5B3F7.3030705@cea.fr> <1425394551.4056.1.camel@thinkpad.lan.sumadev.de> <54F6D731.3090004@cea.fr> <1428953391.22412.40.camel@e130.lan.sumadev.de> <552CD705.9000508@cea.fr> <552CE242.9050307@glondu.net> <552D0BFE.7000904@cea.fr> <1430128317.3427.70.camel@zotac> In-Reply-To: <1430128317.3427.70.camel@zotac> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: [Caml-list] Dependencies between plugins On 27/04/2015 11:51, Gerd Stolpmann wrote: > François, > > I was thinking again about this issue. Introducing a third category > "shared" in addition to byte and native seems to be a bit odd. Actually, > what we really want to have is a second dimension plugin/executable in > addition to the already existing byte/native dimension, so that we can > have: > > - byte + executable (cmo) > - native + executable (cmx) > - byte + plugin (cmo, too) > - native + plugin (cmxs) > This solution represent a more satisfying goal than mine, so even if more META will have to be modified at the end it is better. > > archive(native) = "..." > > as > > archive(native,executable) = "..." > > if there is no other reference to the executable predicate. This would > be a special fixup after parsing META. After a transition phase (say, > two years from now on) we would consider archive(native) as an error. An error? archive(native) will remain a special case? > The upcoming META lint will report this issue. Nice. > > This way, the existing META files can still be used for some time, > including those specifying plugins. There is no hurry in changing this > detail. However, you are absolutely right that the current use of > "plugin" breaks the way the predicates are defined, and in the long term > this is worth fixing. > Great! Do you need some help for implementing all of that? -- François