From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 0D46D7F1AA for ; Wed, 9 Sep 2015 22:06:35 +0200 (CEST) IronPort-PHdr: 9a23:fl313Baxej5unvAdflAdrNv/LSx+4OfEezUN459isYplN5qZpcS9bnLW6fgltlLVR4KTs6sC0LqK9fm8EjVcu96oizMrTt9lb1c9k8IYnggtUoauKHbQC7rUVRE8B9lIT1R//nu2YgB/Ecf6YEDO8DXptWZBUiv2OQc9HOnpAIma153xjLDuvcSPKFwU3nKUWvBbElaflU3prM4YgI9veO4a6yDihT92QdlQ3n5iPlmJnhzxtY+a9Z9n9DlM6bp6r5YTGY2zRakzTKRZATI6KCh1oZSz7ViQBTeIs1wXW2AS2j9BAgzE6h6yepbqrmOuveN43GyePNbqZbEyQzWrqalxHkzGkiACYgQ++mzNloRVkaZfrQjp8wZ4yYPOfMeQKf56c7mHVdwfTGtFGM1WUnoSUcuHc4ITAr9Zbq5jpI7nqg5L9EPmCA== Authentication-Results: mail3-smtp-sop.national.inria.fr; spf=None smtp.pra=robert.muller2@gmail.com; spf=Pass smtp.mailfrom=robert.muller2@gmail.com; spf=None smtp.helo=postmaster@mail-yk0-f173.google.com Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of robert.muller2@gmail.com) identity=pra; client-ip=209.85.160.173; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="robert.muller2@gmail.com"; x-sender="robert.muller2@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of robert.muller2@gmail.com designates 209.85.160.173 as permitted sender) identity=mailfrom; client-ip=209.85.160.173; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="robert.muller2@gmail.com"; x-sender="robert.muller2@gmail.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of postmaster@mail-yk0-f173.google.com) identity=helo; client-ip=209.85.160.173; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="robert.muller2@gmail.com"; x-sender="postmaster@mail-yk0-f173.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A0DYAQD9j/BVlK2gVdFdhGAGgx6nVYZUlRYHPBABAQEBAQEBARABAQEBBwsLCR8wgh2CHxEdARseAxIJAQY3AiQBEQEFASI1h3YBAxKmSIIFgTA+MYtBgWyCeYlwChknDVaEPAEFDpNcgUMFlVaMepksEiOBF4I2HIFwIjOISQEBAQ X-IPAS-Result: A0DYAQD9j/BVlK2gVdFdhGAGgx6nVYZUlRYHPBABAQEBAQEBARABAQEBBwsLCR8wgh2CHxEdARseAxIJAQY3AiQBEQEFASI1h3YBAxKmSIIFgTA+MYtBgWyCeYlwChknDVaEPAEFDpNcgUMFlVaMepksEiOBF4I2HIFwIjOISQEBAQ X-IronPort-AV: E=Sophos;i="5.17,498,1437429600"; d="scan'208";a="145278599" Received: from mail-yk0-f173.google.com ([209.85.160.173]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/AES128-GCM-SHA256; 09 Sep 2015 22:06:34 +0200 Received: by ykei199 with SMTP id i199so33576503yke.0 for ; Wed, 09 Sep 2015 13:06:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=JCZg8XmiDx4GMBTLcr3KNFnLzAtfJihllKLNsO4C28Y=; b=njnsQ5d3sWWRQ/yU9neuJWXKiLPwU2yetZktFzitcbNs83GSN8RDXK1aABmmlF76k7 eoAIqOtaEZaoIflHp+9mBqJZ2y5Lc2Ym2mifJ2vp+NLtvds+oOdxDk47AP2vZNC4Myzf VAJdlIKRImzQZSZVHrTSTBTLtIb7BsxNkrZsII2t2c7XBm4bb+hD39rzEDaQ90L0L94f 8fZfqLvVTDkx0OD5U2/Y4g64FW49lgmB8+VGD8ZAqQqarkVbhrcXFg9HaW944HqH7YS6 B2NVM+dJ4tlz2/Et4dykrobSwbX47oFD4hw3PP9o0MDXIWlq+JgP8IZIMdZc8YcqVyuL c34A== MIME-Version: 1.0 X-Received: by 10.170.121.142 with SMTP id n136mr40963495ykb.116.1441829192883; Wed, 09 Sep 2015 13:06:32 -0700 (PDT) Received: by 10.129.137.193 with HTTP; Wed, 9 Sep 2015 13:06:32 -0700 (PDT) Date: Wed, 9 Sep 2015 16:06:32 -0400 Message-ID: From: Robert Muller To: Ocaml Mailing List Content-Type: multipart/alternative; boundary=001a1137de88de69b7051f5604ed Subject: [Caml-list] .opam structure question --001a1137de88de69b7051f5604ed Content-Type: text/plain; charset=UTF-8 Greetings, probably the wrong forum for such a naive question but hopefully someone can answer it in a couple of keystrokes! I am using OCaml makefiles across slightly skewed versions (4.02.1 and 4.02.3). In my local Makefile, I'm specifying an explicit path to OCamlMakefile: ~/.opam/4.02.1/lib/ocaml-makefile/OCamlMakefile: that includes the release version 4.02.1. But I would prefer for this same Makefile to work on version 4.02.3 too. It seems really wrong to be specifying an explicit version number in a path. On my 4.02.1 version, I was able to replace the version number by "system". This seems to work --- there is a /lib/ocaml-makefile/ folder there. But this same hack did not work on the 4.02.3 system. So my question is, what is the recommended (i.e., modular and portable) way to address an OPAM resource such as OCamlMakefile? I suppose I shouldn't have to know much of anything about the structure of the .opam directory. (?) Thanks! Bob Muller --001a1137de88de69b7051f5604ed Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Greetings, probably the wrong forum for such a naive quest= ion but hopefully someone can answer it in a couple of keystrokes! I am usi= ng OCaml makefiles across slightly skewed versions (4.02.1 and 4.02.3). In = my local Makefile, I'm specifying an explicit path to OCamlMakefile:
~/.opam/4.02.1/lib/ocaml-makefile/OCamlMakefile:

that includes the release version 4.02.1. Bu= t I would prefer for this same Makefile to work on version 4.02.3 too.=C2= =A0 It seems really wrong to be specifying an explicit version number in a = path. On my 4.02.1 version, I was able to replace the version number by &qu= ot;system". This seems to work --- there is a /lib/ocaml-makefile/ fol= der there.=C2=A0 But this same hack did not work on the 4.02.3 system.

So my question is, what is the recommended (i.e., modul= ar and portable) way to address an OPAM resource such as OCamlMakefile? I s= uppose I shouldn't have to know much of anything about the structure of= the .opam directory. (?)

Thanks!
Bob Muller

<= /div>
--001a1137de88de69b7051f5604ed--