On Fri, Jun 5, 2026 at 1:12 PM Andres Freund <[email protected]> wrote: > I'm not particularly concerned about that, tbh. If you suddenly switch which > perl you use, you'll might get some weird errors.
I'm finding that's easy to do by accident, though. The interactions between - Git-for-Windows MSYS, - our full version(s) of MSYS on either C: or D:, - the environment variables we set (esp. MSYSTEM), and - the GITHUB_PATH are fairly unintuitive to me. The windows-vs job pushes Strawberry Perl into the PATH -- but I think that only works because there's no MSYSTEM setting? I haven't found a way to get the windows-mingw job to do the same thing, because it forces its own "native" Perl to take precedence. So if we want the two bash shells to behave similarly, I think some more fundamental things need to be changed first, probably by someone who understands MSYS2 better than I do. Maybe that's just a really small tweak, but I can't see it. --Jacob
