lwt's cmis magically available through ocamlfind but not its dll

[reasonml]

lwt's cmis magically available through ocamlfind but not its dll

[jordwalke]

The ocamlfind in reason-cli isn't meant to be used for anything except debugging reason-cli at the moment. OCamlfind needs to know where stuff is - and so it needs its env variables / config populated correctly. I think that every project should have its own ocamlfind dependency, and its own config that is populated correctly, for that specific project, which will avoid the problem.

OPAM does this for you at the global level which causes some problems (much like the problem you are seeing here). Esy (which reason-cli is based off of) does it at the project level, for your project's specific set of dependencies.

I think we should stop exposing ocamlfind from reason-cli or at least discourage it for anything other than debugging a reason-cli installation. Thoughts?

[bsansouci]

@jordwalke Is there any way to call it something other than ocamlfind so that I don't end up accidentally using it? I want to make sure I have a correct opam install so that things don't sometimes work and sometimes not.

If you think we could get away with not shipping it then that solves my problem :)

[jordwalke]

Yeah, we can realias binaries that are only coincidentally exported to something like reason-cli-ocamlfind. That way they can still be used to debug the installation, but won't conflict.

[bsansouci]

Hey sorry I didn't comment on this for a while.
It'd be awesome if we could make this happen

[bsansouci]

Heyyyy this hit us again, where the ocamlfind that comes with Reason-cli shadows opam’s ocamlfind which makes it unusable.
Any chance we can get this fixed quickly?