-
Notifications
You must be signed in to change notification settings - Fork 496
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Add warning to makepkg-mingw if mingw-w64-file/grep/sed are installed #3798
base: master
Are you sure you want to change the base?
Conversation
Isn't it possible to check if the executable exists? For example, |
Yep, that seems like a better solution. I'll update the pull request. |
do we have some specific evidence for each tool breaking something? Just so we have it documented somewhere. |
This does not look something is breaking but suspicious. Here is a message while using ucrt64 file packaage.
|
There's the discussion in #14313 which provides some examples of dangerous packages. I thought it best to only generate warnings for packages that are part of As a concrete example, the UCRT64 build of
If preferable I can open an issue on Github of the above, for posterity. Granted, If this issue is deemed too small we can of course also remove the warning for |
434066b
to
6379cd3
Compare
I updated the PR to be a single commit (and also updated the revision) |
6379cd3
to
e6ef56b
Compare
Following the discussion in #14313, I've tried to implement a check in
makepkg-mingw
to remediate the issue a little bit.Unfortunately, the
pacman -Q
query takes around 1.1 seconds (at least on my machine), I couldn't find a faster way to implement this however.