-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Windows] Removed Git internal tools from PATH #1648
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @al-cheb! I'm really grateful for seeing this moving forward. Please, see comments below, specially regarding the manipulation of the PATH.
OpenSSL just released 1.1.1h, and I was reminded of an issue. From a related issue discussion:
The popular MSVC OpenSSL build places OpenSSL dll's in System32. I can't test it right now, but this may cause conflicts with MSYS2/MinGW tools loading those files? I know in the past that I've renamed them in various Actions/AppVeyor scripts. If users reshuffle Path, it isn't an issue. And, I don't recall if it was a matter of MSYS2 OpenSSL failing install and then 'CI' resolving the dll's to the System32 files. That isn't your problem, but can produce very confusing results. |
Could you please review the first part of PR to remove git internal tools from PATH? Changes:
Shells
Notes:
|
@al-cheb, as commented in #1648 (comment), I believe there should be a stronger warning about relying on msys64 being added to the PATH by default. The proposed notes are informative only. Apart from that, LGTM. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Description
Topic discussion: #1525
Related issue:
#1525
Check list