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 41A4B7F1AA for ; Wed, 9 Sep 2015 22:26:24 +0200 (CEST) IronPort-PHdr: 9a23:kMgfgR2CZb0YXiu2smDT+DRfVm0co7zxezQtwd8ZsegeLPad9pjvdHbS+e9qxAeQG96Lt7Qd16GP7/CocFdDyKjCmUhKSIZLWR4BhJdetC0bK+nBN3fGKuX3ZTcxBsVIWQwt1Xi6NU9IBJS2PAWK8TWM5DIfUi/yKRBybrysXNWC04Lui6vrp82bSj4LrQT+SIs6FA+xowTVu5teqqpZAYF19CH0pGBVcf9d32JiKAHbtR/94sCt4MwrqHwI6LoJvvRNWqTifqk+UacQTHF/azh0t4XXskz5SgGC/GdUd3gSlhdSS1zf6xv3RIu3tzb+sudnggGVOMT3SfY/XjH0vIlxTxq9oTwHNiU5uEjYg9ZvhaYT9BuurgZgyoqNMd7IHPV7d6LZO9gdQDwSDY5qSyVdD9bkPMM0BO0bMLMd9tGlqg== Authentication-Results: mail2-smtp-roc.national.inria.fr; spf=None smtp.pra=agarwal1975@gmail.com; spf=Pass smtp.mailfrom=agarwal1975@gmail.com; spf=None smtp.helo=postmaster@mail-qg0-f41.google.com Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of agarwal1975@gmail.com) identity=pra; client-ip=209.85.192.41; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="agarwal1975@gmail.com"; x-sender="agarwal1975@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of agarwal1975@gmail.com designates 209.85.192.41 as permitted sender) identity=mailfrom; client-ip=209.85.192.41; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="agarwal1975@gmail.com"; x-sender="agarwal1975@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-qg0-f41.google.com) identity=helo; client-ip=209.85.192.41; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="agarwal1975@gmail.com"; x-sender="postmaster@mail-qg0-f41.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A0BOAQCmlfBVmynAVdFdhGAGgx66EodwAoE8BzoSAQEBAQEBAQEQAQEBAQEGCwsJIS6CHYIHAQEDARIRHQEbHQEDAQsGBQQHNwICIQEBEQEFARwGEwgah3YBAwoIqF6BMD4xi0GBbIJ5iWsKGScNVoQWAQEBAQEBAQMBAQEBAQEBARQBBQ6LYIJPgj0HgmmBQwWMd4hYB4sNgW2TPIVwEiOBF4IpDRyBcCIziEkBAQE X-IPAS-Result: A0BOAQCmlfBVmynAVdFdhGAGgx66EodwAoE8BzoSAQEBAQEBAQEQAQEBAQEGCwsJIS6CHYIHAQEDARIRHQEbHQEDAQsGBQQHNwICIQEBEQEFARwGEwgah3YBAwoIqF6BMD4xi0GBbIJ5iWsKGScNVoQWAQEBAQEBAQMBAQEBAQEBARQBBQ6LYIJPgj0HgmmBQwWMd4hYB4sNgW2TPIVwEiOBF4IpDRyBcCIziEkBAQE X-IronPort-AV: E=Sophos;i="5.17,498,1437429600"; d="scan'208";a="176747379" Received: from mail-qg0-f41.google.com ([209.85.192.41]) by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/AES128-GCM-SHA256; 09 Sep 2015 22:26:23 +0200 Received: by qgt47 with SMTP id 47so18556217qgt.2 for ; Wed, 09 Sep 2015 13:26:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=fxy3KhZEubYPJr2V4baQ3uHmL46s8Y7FrWTpxtLvZFI=; b=ogYeMT27PIDnjLyflGokafwDj1J5r8zrcPs8JEqLFPdurN4XBIVbcZ/rndoeTaZz7a I0n1ehlr4d33nUvnKTz6odVf2UDcZGj4VmTF5hbWrLQU97gx//fFyZ2IfXNopuNCxwqS 504VovjIraT9n/NcVpI4PeaJ/NGjP0F8+vSNIpAPhIVK9aB6uMo/WIqRtUxbjRB86T/Z YrLlNhzlIke9rZCnFm57885vb8jZJf263GSV22ZuDmfBN7qM1Z/UXF5HAMq7i2uwOf+S BW/amCv8yrVIjpgTiiYhaMu2Akl6sWB9cPKEDm1bUcPId6io2WY/7sgO+yd4ygWiLPpD Dajw== X-Received: by 10.141.23.149 with SMTP id z143mr47796739qhd.67.1441830382182; Wed, 09 Sep 2015 13:26:22 -0700 (PDT) MIME-Version: 1.0 Received: by 10.55.8.6 with HTTP; Wed, 9 Sep 2015 13:26:02 -0700 (PDT) In-Reply-To: References: From: Ashish Agarwal Date: Wed, 9 Sep 2015 16:26:02 -0400 Message-ID: To: Robert Muller Cc: Ocaml Mailing List Content-Type: multipart/alternative; boundary=001a11423944c1be1f051f564b60 Subject: Re: [Caml-list] .opam structure question --001a11423944c1be1f051f564b60 Content-Type: text/plain; charset=UTF-8 > But this same hack did not work on the 4.02.3 system. That probably just means you didn't install OCamlMakefile in that switch. You can get paths to library folders using opam itself, e.g. $ opam config var ocaml-makefile:lib /home/alice/.opam/4.02.1/lib/ocaml-makefile You can see the list of all variables available by running `opam config list`. In the output you see, you can replace PKG with any opam package name. On Wed, Sep 9, 2015 at 4:06 PM, Robert Muller wrote: > 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 > --001a11423944c1be1f051f564b60 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
> But this same hack did not= work on the 4.02.3 system.

That probably just means you didn't = install OCamlMakefile in that switch.

You can get paths to library f= olders using opam itself, e.g.

$ opam config var ocaml-makefile:lib<= br>/home/alice/.opam/4.02.1/lib/ocaml-makefile

You can see the list = of all variables available by running `opam config list`. In the output you= see, you can replace PKG with any opam package name.


On Wed, Sep 9, 2015 at 4:06 PM, Robert Muller <robert.muller2@g= mail.com> wrote:
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 t= his same Makefile to work on version 4.02.3 too.=C2=A0 It seems really wron= g to be specifying an explicit version number in a path. On my 4.02.1 versi= on, I was able to replace the version number by "system". This se= ems to work --- there is a /lib/ocaml-makefile/ folder there.=C2=A0 But thi= s 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. (?)

Tha= nks!
Bob Muller


--001a11423944c1be1f051f564b60--