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 mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id 2A77B7F30A for ; Sun, 10 Mar 2013 17:27:00 +0100 (CET) Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of gabriel.scherer@gmail.com) identity=pra; client-ip=209.85.214.43; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="gabriel.scherer@gmail.com"; x-sender="gabriel.scherer@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of gabriel.scherer@gmail.com designates 209.85.214.43 as permitted sender) identity=mailfrom; client-ip=209.85.214.43; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="gabriel.scherer@gmail.com"; x-sender="gabriel.scherer@gmail.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@mail-bk0-f43.google.com) identity=helo; client-ip=209.85.214.43; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="gabriel.scherer@gmail.com"; x-sender="postmaster@mail-bk0-f43.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AmEBADyzPFHRVdYriGdsb2JhbABDxgEIFg4BAQEKCRQUBCSCbQEbHgMSEDAtAREBBQGINQEDDwybCoJyjDKCe4NpChknDVmIfAEFDI8fgyoDllWBHo11FimCd4E3Ow X-IPAS-Result: AmEBADyzPFHRVdYriGdsb2JhbABDxgEIFg4BAQEKCRQUBCSCbQEbHgMSEDAtAREBBQGINQEDDwybCoJyjDKCe4NpChknDVmIfAEFDI8fgyoDllWBHo11FimCd4E3Ow X-IronPort-AV: E=Sophos;i="4.84,819,1355094000"; d="scan'208";a="6322598" Received: from mail-bk0-f43.google.com ([209.85.214.43]) by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/RC4-SHA; 10 Mar 2013 17:26:59 +0100 Received: by mail-bk0-f43.google.com with SMTP id jm19so1374680bkc.30 for ; Sun, 10 Mar 2013 09:26:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:from:date:message-id:subject:to :content-type; bh=S7MsmxOshKNMDCtBwaWasNdxvhbRpgKZwxoiZAY7U8o=; b=JQoTFf267P3bFDnFe0e+VeadajCsKuz4tA9mtVJy+NvoEB/T2PP5tvw+CyxnwvbNWi rmFYbtyPVZoCKMctGHwE5Tuj52YZ6jy1sqj95+5NMV08mOIKOoCYrqzaS5xw3S1FHYEW Fkz3DpLxnkbYOBM9Dq3H1enREzfXGOBDeYWhXV8SUqRelbCsLmsU4Zt8xzax/k4pofHB IRoL2tTVBgrCsCQmLtHWH/lACJdgKGkvSgidybcTEGiovdazK3z1nSDiw+1ms40joi86 3S3yetZzfxS5hyBKTSy5qZYbW1t9GP4RLZuNOZ/PZYWY/ewYIfctNwIiRy6a11BagGAg UAcA== X-Received: by 10.204.200.131 with SMTP id ew3mr3543866bkb.103.1362932819203; Sun, 10 Mar 2013 09:26:59 -0700 (PDT) MIME-Version: 1.0 Received: by 10.205.83.144 with HTTP; Sun, 10 Mar 2013 09:26:19 -0700 (PDT) From: Gabriel Scherer Date: Sun, 10 Mar 2013 17:26:19 +0100 Message-ID: To: caml-list@inria.fr Content-Type: text/plain; charset=ISO-8859-1 Subject: [Caml-list] If you distribute oasis' setup.ml with your software, please use a recent (>= 0.3.0) version of Oasis The number of packages available through OPAM that list "oasis" as a dependency (see list below) is too high -- oasis being designed to let developers pre-generate setup.ml to avoid any actual dependency on it. The reason for this is a glitch in old versions of Oasis (< 0.3.0) that makes the generated setup.ml break with OCaml >= 4.00.0; OPAM packagers list oasis as a dependency to regenerate a fixed setup.ml at compilation time. This is the case in particular for the latest versions of the following packages: - ANSITerminal* - bench* - ocaml-expect - ocaml-posix-resource - ocaml-radixtree - ocaml-sqlexpr - optimization1d* - root1d* (*): oasis is the only dependency besides the ubiquitous ocamlfind If you distribute setup.ml in your source releases, please make sure that it is generated with a recent version of Oasis (>= 0.3.0). This allows to remove oasis (and its four own dependencies) from the dependencies of your package. You can check which version of Oasis a given setup.ml comes from with the command: ocaml setup.ml -version If your package provides a setup.ml with version >= 0.3.0, and "oasis setup" is still present in the "build" field of OPAM metadata description (or "oasis" marked as a dependency for no other reason), this is a packaging bug that you should report to the relevant package maintainer or on the opam repository bugtracker ( https://github.com/OCamlPro/opam-repository/issues/ ). PS: I learned about the bad interaction between Oasis < 0.3.0 and OCaml >= 4.00.0 from Anil Madhavapeddy in the following bugtracker item: https://github.com/OCamlPro/opam-repository/issues/496