Fred Hebert

Well for your example with one/three, I don't quite know. The environment setting does specify using absolute paths: https://github.com/erlang/rebar3/blob/dc3eca5aaf7b7afd9c6c07adbe21a2d07b8a8670/apps/rebar/src/rebar_env.erl#L43 but it sets the path based on the current working directory...

Well that value is not set by rebar3 ever, it is set _for_ rebar3. It could for example be set by default but not used with the rebar3 bare compiler...

Even if we changed the hook mechanism to specifically know which commands are run so that the value is overriden in case of a bare compile call so it runs...

Maybe we could set a value that we guarantee only exists when being called by the bare compiler (we clear it if not) which would indicate a way to do...

Yeah. That's because they have entirely different compiling models. We're sort of stuck with that. Rebar3 gave full standalone modes to Mix and had to write custom compiler extensions to...

Another gotcha here is that setting this mechanism means that you may end up with an unbuildable project if two dependencies set mutually incompatible versions despite many of them being...

I think it _should_ be possible. I think a `minimum_rebar_version` config that is only read at the top-level could make sense. I still don't think that a `selected_rebar_version` argument is...

> Some projects are using it in order to avoid breaking the CI pipeline because of a new version of rebar3 is published. Your pipeline will break every time a...

I cannot replicate this in general. Is this on a shared filesystem in a virtual machine? Those things end up often having bugs that exist nowhere else. Can you also...

Yeah if it works on the home directory and it works but not on the virtual machine filesystems, I assume the problem is with the virtual machine filesystem's semantics. We...