Dear Opam Team,

 

first let me say that I am using the Cygwin MinGW cross opam from https://fdopen.github.io/opam-repository-mingw/installation/.

 

I have the call to .opam/opam-init/init.sh in my .bach_profile file.

 

I observe two obscurities with this setup:

 

1.)    It is really hard to get rid of the opam path settings, I guess cause of the environment hook installed. E.g. although opam env –revert displays the correct original “pre opam” PATH, evaluating with eval $(opam env –revert) does not have the desired effect – the PATH is exactly as before. I guess the environment hook immediately sets it back it. How can I temporarily get back to my original PATH?

2.)    Apparently the MANPATH gets longer each time I execute a command in bash. E.g. when I do a few times “echo $MANPATH | wc” the length displayed by wc increases each time (by one additional reference to the opam man path). This is unfortunate because the total environment of a process is quite limited under Cygwin/windows (I think to 8k).

 

Is this specific to the MinGW cross opam or is this a general problem?

 

Do others have the call to .opam/opam-init/init.sh in there profile or a simple eval $(opam env)? What is the advantage of this rather invasive hook?

 

Best regards,

 

Michael