-
Notifications
You must be signed in to change notification settings - Fork 55
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
MSYS2's installation annoyingly requires pacman.exe termination #20
Comments
pacman -Sy We use these steps when doing upgrades. In cas something is installed in 2nd step, you need to restart msys2 shell |
Yeah, but when you restart the shell, is pacman.exe still running? This is new behavior (it didn't previously happen). |
I just checked, and
to not wait for input. Instead, it returns to the shell, which seems unwise. pacman.exe terminates and nothing appears to go wrong after red-Xing the window, but I don't think I want to directly disobey MSYS2's warning, and their wiki doesn't suggest |
I haven't seen this happen with the 20161025 build, but maybe that's because pacman hasn't been updated since then. |
Right now, it appears that a gibberish-named process needs to be terminated, which is actually worse than needing to terminate pacman.exe. |
Right now, I'm not observing either pacman.exe or the gibberish-named process lingering. However, the "Terminal" hangs after the first invocation of |
With the 20170918 build, the lingering pacman.exe and hanging Terminal are gone, but the gibberish-named process is back. |
The 2021-07-25 build appears to behave properly. |
MSYS2's installation process, as described by my README.md, has become very annoying. One part will disappear (the
update-core
step) when the base archive is updated, but that won't fix the major new annoyance.Specifically, when MSYS2 must be recycled, sometimes
pacman.exe
needs to be terminated manually.It would be great if MSYS2 could be fixed somehow to not require manual termination of processes. Having to red-X the window repeatedly is tolerable, but no more.
The text was updated successfully, but these errors were encountered: