[opam-devel] Conditional build instructions for pinned packages

[Thomas Gazagnaire]

> Having some constraints to indicate a pinned package (or a development remote as opposed to an archive) seems reasonable.  Could you create a bug about this on the tracker?

Indeed.

You might also try a cumbersome workaround fro your issue: if you define `OPAM_foo=true` in your shell then "%{foo}%" will be evaluated to `true` in your OPAM filters. 

--
Thomas


> 
> -anil
> 
> On 2 Jul 2013, at 16:53, Daniel Bünzli <daniel.buenzli at erratique.ch> wrote:
> 
>> Hello, 
>> 
>> I'd like to make my released opam packages pinable with their corresponding git repos. 
>> 
>> For that I need to invoke a special script *only whenever* I build from a git checkout. This script prepares the sources, injects the right version number so that ocamlfind correctly identifies the installed version and generates the oasis artefacts:
>> 
>> build: [
>> ["devel/pkg-opam-git-setup" ] { WHAT CAN I WRITE HERE }
>> ["ocaml" "setup.ml" "-configure" "--prefix" "%{prefix}%" ]
>> ["ocaml" "setup.ml" "-build"]
>> ["ocaml" "setup.ml" "-install"]
>> 
>> ]
>> 
>> So for "WHAT CAN I WRITE HERE" is it possible to either test for `devel/pkg-opam-git-setup` existence (it is not in the release tarballs) or is there some kind of special variable to test that indicates a pinned status ? 
>> 
>> Thanks, 
>> 
>> Daniel
>> 
>> 
>> _______________________________________________
>> opam-devel mailing list
>> opam-devel at lists.ocaml.org
>> http://lists.ocaml.org/listinfo/opam-devel
>> 
> 
> _______________________________________________
> opam-devel mailing list
> opam-devel at lists.ocaml.org
> http://lists.ocaml.org/listinfo/opam-devel