|
OPAM does have some handling of env variable extension ; the documentation is indeed lacking though, but we do have the following in the dev-manual (for opam files):
```
<file> :=
...
?env: [ <env>+ ]
<env> := IDENT <eq> STRING
<eq> := â=â | â+=â | â=+â | â:=â | â=:â
* env is the list of environment variables to set in the given compiler switch:
â VAR = "value" set the variable to the given value;
â VAR += "value" prepend the given value to the variable;
â VAR =+ "value" append the given value to the variable;
â VAR := "value" prepend the given value to the variable, separated by a colon. If the variable
was empty, add the colon anyway.
â VAR =: "value" append the given value to the variable, separated by a colon. If the variable
was empty, add the colon anyway.
```
Le jeudi 21 aoÃt 2014, 10:08:36 Anil Madhavapeddy a ÃcritÂ:
> On 21 Aug 2014, at 10:00, Thomas Gazagnaire <thomas@xxxxxxxxxxxxxx> wrote:
>
> >>> I'm settting up a 4.01 switch with profiling on.
> >>
> >> Thanks!
> >
> > done, I've set OCAMLPARAM to set -g and -p to all ocamlc/ocamlopt invocation in the 4.01.0+profile switch. Feel free to modify the compiler description to fill you needs:
> >
> > https://github.com/ocaml/opam-repository/blob/master/compilers/4.01.0/4.01.0%2Bprofile/4.01.0%2Bprofile.comp
>
> This is really useful! The lack of extensibility in the env var bugs me quite a lot, since it's not possible to locally override the OCAMLPARAM with other fields (such as -bin-annot).
>
> Do you think that an OPAM feature request to support a += field in env is worthwhile at this late stage? I'm thinking that this would be useful for environment variables that support colon-separated delimiters (which I believe OCAMLPARAM does, but I can't find any documentation for it in the manual).
>
> -anil
| 
