-
Notifications
You must be signed in to change notification settings - Fork 18
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
Alternative command runner to make (tasks/just/duty) #120
Comments
In the meantime just can be installed via pipx as well. This is a nice surprise since the |
Hi @dalito - what do you think about creating a stand-alone package that takes a From today's dev call, we were a bit wary about introducing a new build system at the cookie-cutter level. We understand the need for simplification of the build process for Windows users (and more generally, our cookie-cutter has a lot of functionality that we want to streamline). Perhaps (in the long term) we decrease the need for |
I think converting from make to just in a reliable way gets too complex quickly. I could not find a good converter to help with creating the justfile from the PR. Also the AI systems were not able to produce good working code based on the makefile as input.
I agree. A simpler config and the core project management commands available in Python (either from linkML or from this cookiecutter repo) would be better than yet another tool. |
Make is problematic for Window users because it is typically not available. It is also quite challenging to write cross-platform shell commands and get escaping right. Make as a full build tool is naturally more complex than required for a simple command runner. Since we only need a command runner here, we may consider some alternatives.
I looked at
For
just
andtasks
binaries are available for all platforms and installation is straight-forward (also on Windows).duty
as a Python tool can be installed bypipx
. Since linkML-project-cookiecutter users are already instructed to usepipx
forcruft
the installation ofduty
as command runner is the simplest one.The syntax of
tasks
andjust
can be learned relatively fast, but I found it clearly more time-consuming than learning to define tasks in Python forduty
. Induty
I already know how to deal with cross-platform compatibility and have all great Python features like f-strings or path-manipulation available. So my favorite isduty
.I wrote a
duties.py
file that mostly matches the currentmakefile
. - PR to come...What do you think in general about this? Does it help? Does it add or reduce complexity?
The text was updated successfully, but these errors were encountered: