For esy, with the bootstrapped builds, we hit issues where the users .bash_profile (which initializes the OPAM repo), can collide with our build commands - bringing in parts of the OPAM environment that break the build.
We should have an option or a way to pass-through arguments to bash, to ignore the .bash_profile.
For
esy, with the bootstrapped builds, we hit issues where the users.bash_profile(which initializes the OPAM repo), can collide with our build commands - bringing in parts of the OPAM environment that break the build.We should have an option or a way to pass-through arguments to bash, to ignore the
.bash_profile.