Skip to content

Make engines executable via version control (Linux, macOS) - #208

Open
bittner wants to merge 1 commit into
lukasmonk:mainfrom
bittner:feature/make-engines-executable
Open

Make engines executable via version control (Linux, macOS)#208
bittner wants to merge 1 commit into
lukasmonk:mainfrom
bittner:feature/make-engines-executable

Conversation

@bittner

@bittner bittner commented Sep 8, 2025

Copy link
Copy Markdown

Another small step towards to allowing this project to be installed and run as a Python package from PyPI.

Puts the executable bit under version control for all engines, which makes running the RunEngines script on Linux (and macOS) a matter of the past.

Related

@lukasmonk

Copy link
Copy Markdown
Owner

When creating the distributions they go with 777. RunEngines is used when updating or adding engines, but in the distribution it goes or has to go with 777. RunEngines will only be necessary, if I have messed up in the process. It's not a tool designed for the user.

@bittner

bittner commented Sep 9, 2025

Copy link
Copy Markdown
Author

That's all fine. The point is that Git can manage file permissions. This way executable files under version control get the correct permissions directly, no need to ensure this in a build process, and during development the application works as expected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants