os/exec.LookPath contains robust logic for looking up paths cross-platform. However, it is always based on the value of the PATH environment variable; there are cases where one might like to employ the same logic but using a PATH that has come from elsewhere. My current motivating example relates to remote build execution where it may be based on an incoming RPC, I expect others to exist in the wild as well.

In terms of prior art, this seems a little similar to os.Expand and os.ExpandEnv which offer the same option of using the environment or not. We can't match the naming convention of those though so the best suggestion I have is exec.LookPathFrom(file, path string) (string, error).

I anticipate the implementation of this being straightforward, and it shouldn't represent significant additional maintenance in future. I'm of course happy to raise the PR if this proposal is accepted.

Alternatives

In the absence of this function, one could set the PATH variable to the desired value, use LookPath, then reset it back again. This is slightly more work but more importantly is mutating global process state, and is therefore not safe to use if multiple goroutines might execute the same code concurrently.

Possibly a more likely solution is that you'd write some code to do this yourself. That isn't so hard on the face of it, but looking at the actual implementation in exec, it seems unlikely that most implementations would be diligent enough to mimic all the cross-platform nuances or the various edge/error cases that are checked. It would of course also be nice to get updates or fixes to it as well (the command path security changes from 1.19 would be a good example of that).