|
While taking care of the installer for blueCFD-Core 2017-1 (Issue #59), it was spotted a considerable flaw in the executable permissions not being preserved properly. |
Answered by
wyldckat
Mar 8, 2022
Replies: 1 comment
|
Technically, in order to recover the correct executable flags, users have to run the following commands: However, it's not that simple when the ACL permissions are not absolute. In other words, if blueCFD-Core is not installed in a folder fully controlled by the user, then this will not work properly, because |
0 replies
Answer selected by
wyldckat
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Technically, in order to recover the correct executable flags, users have to run the following commands:
However, it's not that simple when the ACL permissions are not absolute. In other words, if blueCFD-Core is not installed in a folder fully controlled by the user, then this will not work properly, because
chmod(or MSys2 itself?) can't do its magic on Windows for setting the (non-)executable flag, which relies on some crazy ACL manipulation. This is why we are not able to make the installer get the job done automatically.